Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for Readiness (0.18 sec)

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

      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
      // cause evictions during disruption.
      // +optional
      optional k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 34.5K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/extensions/v1beta1/generated.proto

      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
      // cause evictions during disruption.
      // This is an alpha field and requires enabling DaemonSetUpdateSurge feature gate.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 45.6K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/apps/v1beta2/generated.proto

      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
      // cause evictions during disruption.
      // +optional
      optional k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 36.4K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/discovery/v1/generated.proto

      // indicates an unknown state. In most cases consumers should interpret this
      // unknown state as ready. For compatibility reasons, ready should never be
      // "true" for terminating endpoints, except when the normal readiness
      // behavior is being explicitly overridden, for example when the associated
      // Service has set the publishNotReadyAddresses flag.
      // +optional
      optional bool ready = 1;
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 8K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/core/v1/generated.proto

      // +optional
      optional PodDNSConfig dnsConfig = 26;
    
      // If specified, all readiness gates will be evaluated for pod readiness.
      // A pod is ready when all its containers are ready AND
      // all conditions specified in the readiness gates have status equal to "True"
      // More info: https://git.k8s.io/enhancements/keps/sig-network/580-pod-readiness-gates
      // +optional
      repeated PodReadinessGate readinessGates = 28;
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 255.8K bytes
    - Viewed (0)
Back to top