Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 10 for wait (0.16 sec)

  1. common-protos/k8s.io/api/apps/v1beta1/generated.proto

      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/apps/v1/generated.proto

      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 34.5K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/coordination/v1beta1/generated.proto

    message LeaseSpec {
      // holderIdentity contains the identity of the holder of a current lease.
      // +optional
      optional string holderIdentity = 1;
    
      // leaseDurationSeconds is a duration that candidates for a lease need
      // to wait to force acquire it. This is measure against time of last
      // observed renewTime.
      // +optional
      optional int32 leaseDurationSeconds = 2;
    
      // acquireTime is a time when the current lease was acquired.
      // +optional
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 2.7K bytes
    - Viewed (0)
  4. common-protos/k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto

      // If specified, the time in seconds before the operation should be retried. Some errors may indicate
      // the client must take an alternate action - for those errors this field may indicate how long to wait
      // before taking the alternate action.
      // +optional
      optional int32 retryAfterSeconds = 5;
    }
    
    // TableOptions are used when a Table is requested by the caller.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 53.3K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/apps/v1beta2/generated.proto

      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 36.4K bytes
    - Viewed (0)
  6. common-protos/k8s.io/api/coordination/v1/generated.proto

    message LeaseSpec {
      // holderIdentity contains the identity of the holder of a current lease.
      // +optional
      optional string holderIdentity = 1;
    
      // leaseDurationSeconds is a duration that candidates for a lease need
      // to wait to force acquire it. This is measure against time of last
      // observed renewTime.
      // +optional
      optional int32 leaseDurationSeconds = 2;
    
      // acquireTime is a time when the current lease was acquired.
      // +optional
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 2.6K bytes
    - Viewed (0)
  7. common-protos/k8s.io/api/networking/v1/generated.proto

      // (whether or not they contain an ingress section) are assumed to affect ingress.
      // If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ].
      // Likewise, if you want to write a policy that specifies that no egress is allowed,
      // you must specify a policyTypes value that include "Egress" (since such a policy would not include
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 25.2K bytes
    - Viewed (0)
  8. common-protos/k8s.io/api/admissionregistration/v1/generated.proto

      //       "key": "runlevel",
      //       "operator": "NotIn",
      //       "values": [
      //         "0",
      //         "1"
      //       ]
      //     }
      //   ]
      // }
      //
      // If instead you want to only run the webhook on any objects whose
      // namespace is associated with the "environment" of "prod" or "staging";
      // you will set the selector as follows:
      // "namespaceSelector": {
      //   "matchExpressions": [
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.4K bytes
    - Viewed (0)
  9. common-protos/k8s.io/api/storage/v1beta1/generated.proto

      // operation (because it implements the CSI ControllerPublishVolume()
      // method), and that the Kubernetes attach detach controller should call
      // the attach volume interface which checks the volumeattachment status
      // and waits until the volume is attached before proceeding to mounting.
      // The CSI external-attacher coordinates with CSI volume driver and updates
      // the volumeattachment status when the attach operation is complete.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.9K bytes
    - Viewed (0)
  10. common-protos/k8s.io/api/storage/v1/generated.proto

      // operation (because it implements the CSI ControllerPublishVolume()
      // method), and that the Kubernetes attach detach controller should call
      // the attach volume interface which checks the volumeattachment status
      // and waits until the volume is attached before proceeding to mounting.
      // The CSI external-attacher coordinates with CSI volume driver and updates
      // the volumeattachment status when the attach operation is complete.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.7K bytes
    - Viewed (0)
Back to top