- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 106 for nodes (0.15 sec)
-
common-protos/k8s.io/api/node/v1beta1/generated.proto
// https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md // +optional optional Overhead overhead = 3; // scheduling holds the scheduling constraints to ensure that pods running // with this RuntimeClass are scheduled to nodes that support it. // If scheduling is nil, this RuntimeClass is assumed to be supported by all // nodes. // +optional optional Scheduling scheduling = 4; }
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
common-protos/k8s.io/api/apps/v1/generated.proto
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 34.5K bytes - Viewed (0) -
common-protos/k8s.io/api/apps/v1beta2/generated.proto
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 36.4K bytes - Viewed (0) -
common-protos/k8s.io/api/storage/v1/generated.proto
// refer to a given node as "node1", but the storage system may refer to // the same node as "nodeA". When Kubernetes issues a command to the storage // system to attach a volume to a specific node, it can use this field to // refer to the node name using the ID that the storage system will // understand, e.g. "nodeA" instead of "node1". This field is required. optional string nodeID = 2;
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) -
common-protos/k8s.io/api/node/v1/generated.proto
repeated RuntimeClass items = 2; } // Scheduling specifies the scheduling constraints for nodes supporting a // RuntimeClass. message Scheduling { // nodeSelector lists labels that must be present on nodes that support this // RuntimeClass. Pods using this RuntimeClass can only be scheduled to a // node matched by this selector. The RuntimeClass nodeSelector is merged
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
common-protos/k8s.io/api/node/v1alpha1/generated.proto
// https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md // +optional optional Overhead overhead = 2; // scheduling holds the scheduling constraints to ensure that pods running // with this RuntimeClass are scheduled to nodes that support it. // If scheduling is nil, this RuntimeClass is assumed to be supported by all // nodes. // +optional optional Scheduling scheduling = 3; }
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 5K bytes - Viewed (0) -
common-protos/k8s.io/api/extensions/v1beta1/generated.proto
// An object that describes the pod that will be created. // The DaemonSet will create exactly one copy of this pod on every node // that matches the template's node selector (or on every node if no node // selector is specified). // More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 45.6K bytes - Viewed (0) -
common-protos/k8s.io/api/storage/v1beta1/generated.proto
// not share the same nomenclature for nodes. For example, Kubernetes may // refer to a given node as "node1", but the storage system may refer to // the same node as "nodeA". When Kubernetes issues a command to the storage // system to attach a volume to a specific node, it can use this field to // refer to the node name using the ID that the storage system will // understand, e.g. "nodeA" instead of "node1". This field is required.
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) -
common-protos/k8s.io/api/networking/v1alpha1/generated.proto
// ClusterCIDR represents a single configuration for per-Node Pod CIDR // allocations when the MultiCIDRRangeAllocator is enabled (see the config for // kube-controller-manager). A cluster may have any number of ClusterCIDR // resources, all of which will be considered when allocating a CIDR for a // Node. A ClusterCIDR is eligible to be used for a given Node when the node // selector matches the node in question and has free CIDRs to allocate. In
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 6K bytes - Viewed (0) -
docs/distributed/CONFIG.md
```yaml version: v2 address: ":9000" rootUser: "minioadmin" rootPassword: "minioadmin" console-address: ":9001" certs-dir: "/home/user/.minio/certs/" pools: # Specify the nodes and drives with pools - args: - "https://server-example-pool1:9000/mnt/disk{1...4}/" - "https://server{1...2}-pool1:9000/mnt/disk{1...4}/" - "https://server3-pool1:9000/mnt/disk{1...4}/"
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 03 15:54:03 GMT 2024 - 4.2K bytes - Viewed (0)