Reference documentation and code samples for the Google Anthos Multi Cloud V1 Client class NodeKubeletConfig.
Configuration for node pool kubelet options.
Generated from protobuf message google.cloud.gkemulticloud.v1.NodeKubeletConfig
Namespace
Google \ Cloud \ GkeMultiCloud \ V1Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ insecure_kubelet_readonly_port_enabled
bool
Optional. Enable the insecure kubelet read only port.
↳ cpu_manager_policy
string
Optional. Control the CPU management policy on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed. * * "none": the default, which represents the existing scheduling behavior. * * "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified.
↳ cpu_cfs_quota
bool
Optional. Enable CPU CFS quota enforcement for containers that specify CPU limits. This option is enabled by default which makes kubelet use CFS quota ( https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt ) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified.
↳ cpu_cfs_quota_period
string
Optional. Set the CPU CFS quota period value 'cpu.cfs_period_us'. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration. The default value is '100ms' if unspecified.
↳ pod_pids_limit
int|string
Optional. Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304.
getInsecureKubeletReadonlyPortEnabled
Optional. Enable the insecure kubelet read only port.
bool
setInsecureKubeletReadonlyPortEnabled
Optional. Enable the insecure kubelet read only port.
var
bool
$this
getCpuManagerPolicy
Optional. Control the CPU management policy on the node.
See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed.
- "none": the default, which represents the existing scheduling behavior.
- "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified.
string
hasCpuManagerPolicy
clearCpuManagerPolicy
setCpuManagerPolicy
Optional. Control the CPU management policy on the node.
See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed.
- "none": the default, which represents the existing scheduling behavior.
- "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified.
var
string
$this
getCpuCfsQuota
Optional. Enable CPU CFS quota enforcement for containers that specify CPU limits.
This option is enabled by default which makes kubelet use CFS quota ( https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt ) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified.
bool
hasCpuCfsQuota
clearCpuCfsQuota
setCpuCfsQuota
Optional. Enable CPU CFS quota enforcement for containers that specify CPU limits.
This option is enabled by default which makes kubelet use CFS quota ( https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt ) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified.
var
bool
$this
getCpuCfsQuotaPeriod
Optional. Set the CPU CFS quota period value 'cpu.cfs_period_us'.
The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration. The default value is '100ms' if unspecified.
string
hasCpuCfsQuotaPeriod
clearCpuCfsQuotaPeriod
setCpuCfsQuotaPeriod
Optional. Set the CPU CFS quota period value 'cpu.cfs_period_us'.
The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration. The default value is '100ms' if unspecified.
var
string
$this
getPodPidsLimit
Optional. Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304.
int|string
hasPodPidsLimit
clearPodPidsLimit
setPodPidsLimit
Optional. Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304.
var
int|string
$this
