Search Options

Results per page
Sort
Preferred Languages
Advance

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

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

      // +listType=atomic
      optional bytes request = 1;
    
      // signerName indicates the requested signer, and is a qualified name.
      //
      // List/watch requests for CertificateSigningRequests can filter on this field using a "spec.signerName=NAME" fieldSelector.
      //
      // Well-known Kubernetes signers are:
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 11.6K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/admissionregistration/v1/generated.proto

      // webhook. Match conditions filter requests that have already been matched by the rules,
      // namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests.
      // There are a maximum of 64 match conditions allowed.
      //
      // The exact matching logic is (in order):
      //   1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.4K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/storage/v1beta1/generated.proto

    // capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler
    // compares the MaximumVolumeSize against the requested size of pending volumes
    // to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back
    // to a comparison against the less precise Capacity. If that is also unset,
    // the scheduler assumes that capacity is insufficient and tries some other
    // node.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.9K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/storage/v1/generated.proto

    // capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler
    // compares the MaximumVolumeSize against the requested size of pending volumes
    // to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back
    // to a comparison against the less precise Capacity. If that is also unset,
    // the scheduler assumes that capacity is insufficient and tries some other
    // node.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.7K bytes
    - Viewed (0)
Back to top