Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for compare (0.14 sec)

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

    //
    // They are consumed by the kube-scheduler when a CSI driver opts into
    // 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,
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 9.4K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/storage/v1beta1/generated.proto

      optional string nodeID = 2;
    
      // topologyKeys is the list of keys supported by the driver.
      // When a driver is initialized on a cluster, it provides a set of topology
      // keys that it understands (e.g. "company.com/zone", "company.com/region").
      // 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.
    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)
  3. common-protos/k8s.io/api/autoscaling/v2/generated.proto

    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    // Kubernetes, and have special scaling options on top of those available to
    // normal per-pod metrics using the "pods" source.  Only one "target" type
    // should be set.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.3K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/autoscaling/v1/generated.proto

    // Kubernetes, as specified in the requests and limits, describing a single container in
    // each of the pods of the current scale target(e.g. CPU or memory). The values will be
    // averaged together before being compared to the target. Such metrics are built into
    // Kubernetes, and have special scaling options on top of those available to
    // normal per-pod metrics using the "pods" source. Only one "target" type
    // should be set.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 22K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/autoscaling/v2beta2/generated.proto

    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    // Kubernetes, and have special scaling options on top of those available to
    // normal per-pod metrics using the "pods" source.  Only one "target" type
    // should be set.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21K bytes
    - Viewed (0)
  6. common-protos/k8s.io/api/autoscaling/v2beta1/generated.proto

    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    // Kubernetes, and have special scaling options on top of those available to
    // normal per-pod metrics using the "pods" source.  Only one "target" type
    // should be set.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.2K bytes
    - Viewed (0)
  7. common-protos/k8s.io/api/storage/v1/generated.proto

      optional string nodeID = 2;
    
      // topologyKeys is the list of keys supported by the driver.
      // When a driver is initialized on a cluster, it provides a set of topology
      // keys that it understands (e.g. "company.com/zone", "company.com/region").
      // 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.
    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