Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for popular (0.18 sec)

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

    // CSI drivers do not need to create the CSINode object directly. As long as
    // they use the node-driver-registrar sidecar container, the kubelet will
    // automatically populate the CSINode object for the CSI driver as part of
    // kubelet plugin registration.
    // CSINode has the same name as a node. If the object is missing, it means either
    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)
  2. common-protos/k8s.io/api/core/v1/generated.proto

      // dataSourceRef specifies the object from which to populate the volume with data, if a non-empty
      // volume is desired. This may be any object from a non-empty API group (non
      // core object) or a PersistentVolumeClaim object.
      // When this field is specified, volume binding will only succeed if the type of
      // the specified object matches some installed volume populator or dynamic
      // provisioner.
    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)
  3. common-protos/k8s.io/api/storage/v1/generated.proto

    // CSI drivers do not need to create the CSINode object directly. As long as
    // they use the node-driver-registrar sidecar container, the kubelet will
    // automatically populate the CSINode object for the CSI driver as part of
    // kubelet plugin registration.
    // CSINode has the same name as a node. If the object is missing, it means either
    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