mirror of
https://github.com/kubernetes/client-go.git
synced 2026-05-15 03:33:11 +00:00
Update comment and regenerate API docs
Kubernetes-commit: dede11365be89384facd8226bb547f186446bee5
This commit is contained in:
committed by
Kubernetes Publisher
parent
27966b2574
commit
2e882c6ea6
@@ -178,8 +178,21 @@ type CSIDriverSpecApplyConfiguration struct {
|
||||
//
|
||||
// Default behavior if unset is to pass tokens in the VolumeContext field.
|
||||
ServiceAccountTokenInSecrets *bool `json:"serviceAccountTokenInSecrets,omitempty"`
|
||||
// PreventPodSchedulingIfMissing indicates that the CSI driver wants to prevent pod scheduling if the CSI driver
|
||||
// on the node is missing.
|
||||
// PreventPodSchedulingIfMissing indicates that the CSI driver wants to prevent pod
|
||||
// scheduling if the CSI driver on the node is missing.
|
||||
//
|
||||
// Enabling this option will prevent the scheduler (or any other
|
||||
// component which embeds default scheduler such as cluster-autoscaler) from
|
||||
// scheduling pods to nodes where CSI driver is not installed.
|
||||
//
|
||||
// For components(such as cluster-autoscaler) that embed the scheduler and run
|
||||
// pod placement simulations using scheduler plugins, they MUST be aware of
|
||||
// CSI driver registration information via CSINode object. They must create simulated
|
||||
// CSINode objects in addition to Node objects during scheduling simulation, otherwise
|
||||
// if PreventPodSchedulingIfMissing is enabled globally for CSIDriver object, any
|
||||
// newly created node may be rejected by the scheduler because of missing CSI driver
|
||||
// information from the node.
|
||||
//
|
||||
// This is an alpha feature and requires the VolumeLimitScaling feature gate to be enabled.
|
||||
// Default is "false".
|
||||
PreventPodSchedulingIfMissing *bool `json:"preventPodSchedulingIfMissing,omitempty"`
|
||||
|
||||
@@ -178,8 +178,21 @@ type CSIDriverSpecApplyConfiguration struct {
|
||||
//
|
||||
// Default behavior if unset is to pass tokens in the VolumeContext field.
|
||||
ServiceAccountTokenInSecrets *bool `json:"serviceAccountTokenInSecrets,omitempty"`
|
||||
// PreventPodSchedulingIfMissing indicates that the CSI driver wants to prevent pod scheduling if the CSI driver
|
||||
// on the node is missing.
|
||||
// PreventPodSchedulingIfMissing indicates that the CSI driver wants to prevent pod
|
||||
// scheduling if the CSI driver on the node is missing.
|
||||
//
|
||||
// Enabling this option will prevent the scheduler (or any other
|
||||
// component which embeds default scheduler such as cluster-autoscaler) from
|
||||
// scheduling pods to nodes where CSI driver is not installed.
|
||||
//
|
||||
// For components(such as cluster-autoscaler) that embed the scheduler and run
|
||||
// pod placement simulations using scheduler plugins, they MUST be aware of
|
||||
// CSI driver registration information via CSINode object. They must create simulated
|
||||
// CSINode objects in addition to Node objects during scheduling simulation, otherwise
|
||||
// if PreventPodSchedulingIfMissing is enabled globally for CSIDriver object, any
|
||||
// newly created node may be rejected by the scheduler because of missing CSI driver
|
||||
// information from the node.
|
||||
//
|
||||
// This is an alpha feature and requires the VolumeLimitScaling feature gate to be enabled.
|
||||
// Default is "false".
|
||||
PreventPodSchedulingIfMissing *bool `json:"preventPodSchedulingIfMissing,omitempty"`
|
||||
|
||||
Reference in New Issue
Block a user