Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 23 of 23 for Down (0.14 sec)

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

      // contain duplicate certificates, or that use PEM block headers.
      //
      // Users of ClusterTrustBundles, including Kubelet, are free to reorder and
      // deduplicate certificate blocks in this file according to their own logic,
      // as well as to drop PEM block headers and inter-block data.
      optional string trustBundle = 2;
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 4.2K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/discovery/v1/generated.proto

      // addresses of this endpoint. The contents of this field are interpreted
      // according to the corresponding EndpointSlice addressType field. Consumers
      // must handle different types of addresses in the context of their own
      // capabilities. This must contain at least one address but no more than
      // 100. These are all assumed to be fungible and clients may choose to only
      // use the first element. Refer to: https://issue.k8s.io/106267
    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)
  3. common-protos/k8s.io/api/storage/v1/generated.proto

      // When a driver is initialized on a node, it provides the same topology keys
      // along with values. Kubelet will expose these topology keys as labels
      // on its own node object.
      // When Kubernetes does topology aware provisioning, it can use this list to
      // determine which labels it should retrieve from the node object and pass
      // back to the driver.
    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