- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for gold (0.2 sec)
-
CREDITS
License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Jun 13 15:34:20 UTC 2024 - 1.7M bytes - Viewed (0) -
src/internal/trace/traceviewer/static/trace_viewer_full.html
if(this._propertyChanged){this._propertyChanged(property,value,old);} if(effects){this._effectEffects(property,value,effects,old,fromAbove);}}
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Nov 21 20:45:06 UTC 2023 - 2.5M bytes - Viewed (0) -
api/openapi-spec/v3/api__v1_openapi.json
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed May 29 22:40:29 UTC 2024 - 1.8M bytes - Viewed (0) -
staging/src/k8s.io/cli-runtime/artifacts/openapi/swagger-with-shared-parameters.json
total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that...
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Feb 20 15:45:02 UTC 2024 - 2.3M bytes - Viewed (0) -
staging/src/k8s.io/cli-runtime/artifacts/openapi/swagger.json
total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that...
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Feb 20 15:45:02 UTC 2024 - 4.5M bytes - Viewed (0)