Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for Connor (0.17 sec)

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

      // when calculating pod topology spread skew. Options are:
      // - Honor: only nodes matching nodeAffinity/nodeSelector are included in the calculations.
      // - Ignore: nodeAffinity/nodeSelector are ignored. All nodes are included in the calculations.
      //
      // If this value is nil, the behavior is equivalent to the Honor policy.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 255.8K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/networking/v1/generated.proto

      // created Ingress resources should prefer using the field. However, even
      // though the annotation is officially deprecated, for backwards compatibility
      // reasons, ingress controllers should still honor that annotation if present.
      // +optional
      optional string ingressClassName = 4;
    
      // defaultBackend is the backend that should handle requests that don't
    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)
  3. common-protos/k8s.io/api/certificates/v1beta1/generated.proto

      //
      // The v1.22+ in-tree implementations of the well-known Kubernetes signers will
      // honor this field as long as the requested duration is not greater than the
      // maximum duration they will honor per the --cluster-signing-duration CLI
      // flag to the Kubernetes controller manager.
      //
      // Certificate signers may not honor this field for various reasons:
      //
      //   1. Old signer that is unaware of the field (such as the in-tree
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 6.7K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/certificates/v1/generated.proto

      //
      // The v1.22+ in-tree implementations of the well-known Kubernetes signers will
      // honor this field as long as the requested duration is not greater than the
      // maximum duration they will honor per the --cluster-signing-duration CLI
      // flag to the Kubernetes controller manager.
      //
      // Certificate signers may not honor this field for various reasons:
      //
      //   1. Old signer that is unaware of the field (such as the in-tree
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 11.6K bytes
    - Viewed (0)
Back to top