File modified: @@ -2212,9 +2212,9 @@ func (o JobSpecOutput) PodFailurePolicy() PodFailurePolicyPtrOutput { // podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods // -// when they are terminating (has a metadata.deletionTimestamp) or failed. -// - Failed means to wait until a previously created Pod is fully terminated (has phase -// Failed or Succeeded) before creating a replacement Pod. +// when they are terminating (has a metadata.deletionTimestamp) or failed. +// - Failed means to wait until a previously created Pod is fully terminated (has phase +// Failed or Succeeded) before creating a replacement Pod. // // When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an beta field. To use this, enable the JobPodReplacementPolicy feature toggle. This is on by default. func (o JobSpecOutput) PodReplacementPolicy() pulumi.StringPtrOutput { @@ -2382,9 +2382,9 @@ func (o JobSpecPtrOutput) PodFailurePolicy() PodFailurePolicyPtrOutput { // podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods // -// when they are terminating (has a metadata.deletionTimestamp) or failed. -// - Failed means to wait until a previously created Pod is fully terminated (has phase -// Failed or Succeeded) before creating a replacement Pod. +// when they are terminating (has a metadata.deletionTimestamp) or failed. +// - Failed means to wait until a previously created Pod is fully terminated (has phase +// Failed or Succeeded) before creating a replacement Pod. // // When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an beta field. To use this, enable the JobPodReplacementPolicy feature toggle. This is on by default. func (o JobSpecPtrOutput) PodReplacementPolicy() pulumi.StringPtrOutput { @@ -2699,9 +2699,9 @@ func (o JobSpecPatchOutput) PodFailurePolicy() PodFailurePolicyPatchPtrOutput { // podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods // -// when they are terminating (has a metadata.deletionTimestamp) or failed. -// - Failed means to wait until a previously created Pod is fully terminated (has phase -// Failed or Succeeded) before creating a replacement Pod. +// when they are terminating (has a metadata.deletionTimestamp) or failed. +// - Failed means to wait until a previously created Pod is fully terminated (has phase +// Failed or Succeeded) before creating a replacement Pod. // // When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an beta field. To use this, enable the JobPodReplacementPolicy feature toggle. This is on by default. func (o JobSpecPatchOutput) PodReplacementPolicy() pulumi.StringPtrOutput { @@ -2869,9 +2869,9 @@ func (o JobSpecPatchPtrOutput) PodFailurePolicy() PodFailurePolicyPatchPtrOutput // podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods // -// when they are terminating (has a metadata.deletionTimestamp) or failed. -// - Failed means to wait until a previously created Pod is fully terminated (has phase -// Failed or Succeeded) before creating a replacement Pod. +// when they are terminating (has a metadata.deletionTimestamp) or failed. +// - Failed means to wait until a previously created Pod is fully terminated (has phase +// Failed or Succeeded) before creating a replacement Pod. // // When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an beta field. To use this, enable the JobPodRe

File modified: @@ -456,10 +456,10 @@ func (o LeaseCandidateSpecOutput) PingTime() pulumi.StringPtrOutput { // PreferredStrategies indicates the list of strategies for picking the leader for coordinated leader election. The list is ordered, and the first strategy supersedes all other strategies. The list is used by coordinated leader election to make a decision about the final election strategy. This follows as - If all clients have strategy X as the first element in this list, strategy X will be used. - If a candidate has strategy [X] and another candidate has strategy [Y, X], Y supersedes X and strategy Y // -// will be used. -// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader -// election will not operate the Lease until resolved. -// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. +// will be used. +// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader +// election will not operate the Lease until resolved. +// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. func (o LeaseCandidateSpecOutput) PreferredStrategies() pulumi.StringArrayOutput { return o.ApplyT(func(v LeaseCandidateSpec) []string { return v.PreferredStrategies }).(pulumi.StringArrayOutput) } @@ -535,10 +535,10 @@ func (o LeaseCandidateSpecPtrOutput) PingTime() pulumi.StringPtrOutput { // PreferredStrategies indicates the list of strategies for picking the leader for coordinated leader election. The list is ordered, and the first strategy supersedes all other strategies. The list is used by coordinated leader election to make a decision about the final election strategy. This follows as - If all clients have strategy X as the first element in this list, strategy X will be used. - If a candidate has strategy [X] and another candidate has strategy [Y, X], Y supersedes X and strategy Y // -// will be used. -// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader -// election will not operate the Lease until resolved. -// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. +// will be used. +// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader +// election will not operate the Lease until resolved. +// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. func (o LeaseCandidateSpecPtrOutput) PreferredStrategies() pulumi.StringArrayOutput { return o.ApplyT(func(v *LeaseCandidateSpec) []string { if v == nil { @@ -709,10 +709,10 @@ func (o LeaseCandidateSpecPatchOutput) PingTime() pulumi.StringPtrOutput { // PreferredStrategies indicates the list of strategies for picking the leader for coordinated leader election. The list is ordered, and the first strategy supersedes all other strategies. The list is used by coordinated leader election to make a decision about the final election strategy. This follows as - If all clients have strategy X as the first element in this list, strategy X will be used. - If a candidate has strategy [X] and another candidate has strategy [Y, X], Y supersedes X and strategy Y // -// will be used. -// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader -// election will not operate the Lease until resolved. -// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. +// will be used. +// - If a candidate has strategy [X, Y] and another candidate has strategy [Y, X], this is a user error and leader +// election will not operate the Lease until resolved. +// (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled. func (o LeaseCandidateSpecPatchOutput) PreferredStrategies() pulumi.StringArrayOutput { return o.ApplyT(func(v

File modified: @@ -38603,13 +38603,13 @@ func (o PersistentVolumeClaimSpecOutput) DataSource() TypedLocalObjectReferenceP // dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef // -// allows any non-core object, as well as PersistentVolumeClaim objects. -// - While dataSource ignores disallowed values (dropping them), dataSourceRef -// preserves all values, and generates an error if a disallowed value is -// specified. -// - While dataSource only allows local objects, dataSourceRef allows objects -// in any namespaces. -// (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled. +// allows any non-core object, as well as PersistentVolumeClaim objects. +// - While dataSource ignores disallowed values (dropping them), dataSourceRef +// preserves all values, and generates an error if a disallowed value is +// specified. +// - While dataSource only allows local objects, dataSourceRef allows objects +// in any namespaces. +// (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled. func (o PersistentVolumeClaimSpecOutput) DataSourceRef() TypedObjectReferencePtrOutput { return o.ApplyT(func(v PersistentVolumeClaimSpec) *TypedObjectReference { return v.DataSourceRef }).(TypedObjectReferencePtrOutput) } @@ -38690,13 +38690,13 @@ func (o PersistentVolumeClaimSpecPtrOutput) DataSource() TypedLocalObjectReferen // dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef // -// allows any non-core object, as well as PersistentVolumeClaim objects. -// - While dataSource ignores disallowed values (dropping them), dataSourceRef -// preserves all values, and generates an error if a disallowed value is -// specified. -// - While dataSource only allows local objects, dataSourceRef allows objects -// in any namespaces. -// (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespac

File modified: @@ -149,12 +149,12 @@ func (o EndpointOutput) TargetRef() corev1.ObjectReferencePtrOutput { // topology contains arbitrary topology information associated with the endpoint. These key/value pairs must conform with the label format. https://kubernetes.io/docs/concepts/overview/working-with-objects/labels Topology may include a maximum of 16 key/value pairs. This includes, but is not limited to the following well known keys: * kubernetes.io/hostname: the value indicates the hostname of the node // -// where the endpoint is located. This should match the corresponding -// node label. -// - topology.kubernetes.io/zone: the value indicates the zone where the -// endpoint is located. This should match the corresponding node label. -// - topology.kubernetes.io/region: the value indicates the region where the -// endpoint is located. This should match the corresponding node label. +// where the endpoint is located. This should match the corresponding +// node label. +// - topology.kubernetes.io/zone: the value indicates the zone where the +// endpoint is located. This should match the corresponding node label. +// - topology.kubernetes.io/region: the value indicates the region where the +// endpoint is located. This should match the corresponding node label. func (o EndpointOutput) Topology() pulumi.StringMapOutput { return o.ApplyT(func(v Endpoint) map[string]string { return v.Topology }).(pulumi.StringMapOutput) } @@ -669,12 +669,12 @@ func (o EndpointPatchOutput) TargetRef() corev1.ObjectReferencePatchPtrOutput { // topology contains arbitrary topology information associated with the endpoint. These key/value pairs must conform with the label format. https://kubernetes.io/docs/concepts/overview/working-with-objects/labels Topology may include a maximum of 16 key/value pairs. This includes, but is not limited to the following well known keys: * kubernetes.io/hostname: the value indicates the hostname of the node // -// where the endpoint is located. This should match the corresponding -// node label. -// - topology.kubernetes.io/zone: the value indicates the zone where the -// endpoint is located. This should match the corresponding node label. -// - topology.kubernetes.io/region: the value indicates the region where the -// endpoint is located. This should match the corresponding node label. +// where the endpoint is located. This should match the corresponding +// node label. +// - topology.kubernetes.io/zone: the value indicates the zone where the +// endpoint is located. This should match the corresponding node label. +// - topology.kubernetes.io/region: the value indicates the region where the +// endpoint is located. This should match the corresponding node label. func (o EndpointPatchOutput) Topology() pulumi.StringMapOutput { return o.ApplyT(func(v EndpointPatch) map[string]string { return v.Topology }).(pulumi.StringMapOutput) }

File modified: @@ -5424,16 +5424,16 @@ func (o HTTPIngressPathOutput) Path() pulumi.StringPtrOutput { // PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. Defaults to ImplementationSpecific. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. Defaults to ImplementationSpecific. func (o HTTPIngressPathOutput) PathType() pulumi.StringPtrOutput { return o.ApplyT(func(v HTTPIngressPath) *string { return v.PathType }).(pulumi.StringPtrOutput) } @@ -5573,16 +5573,16 @@ func (o HTTPIngressPathPatchOutput) Path() pulumi.StringPtrOutput { // PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. Defaults to ImplementationSpecific. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. Defaults to ImplementationSpecific. func (o HTTPIngressPathPatchOutput) PathType() pulumi.StringPtrOutput { return o.ApplyT(func(v HTTPIngressPathPatch) *string { return v.PathType }).(pulumi.StringPtrOutput) } @@ -7479,10 +7479,10 @@ func (o IngressRuleOutput) ToIngressRuleOutputWithContext(ctx context.Context) I

File modified: @@ -130,16 +130,16 @@ func (o HTTPIngressPathOutput) Path() pulumi.StringPtrOutput { // pathType determines the interpretation of the path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. func (o HTTPIngressPathOutput) PathType() pulumi.StringOutput { return o.ApplyT(func(v HTTPIngressPath) string { return v.PathType }).(pulumi.StringOutput) } @@ -279,16 +279,16 @@ func (o HTTPIngressPathPatchOutput) Path() pulumi.StringPtrOutput { // pathType determines the interpretation of the path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. func (o HTTPIngressPathPatchOutput) PathType() pulumi.StringPtrOutput { return o.ApplyT(func(v HTTPIngressPathPatch) *string { return v.PathType }).(pulumi.StringPtrOutput) } @@ -3270,9 +3270,9 @@ func (o IngressPortStatusOutput) ToIngressPortStatusOutputWithContext(ctx contex // error is to record the problem with the service port The format of the error shall comply with the following rules: - built-in error values shall be spe

File modified: @@ -130,16 +130,16 @@ func (o HTTPIngressPathOutput) Path() pulumi.StringPtrOutput { // PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. Defaults to ImplementationSpecific. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. Defaults to ImplementationSpecific. func (o HTTPIngressPathOutput) PathType() pulumi.StringPtrOutput { return o.ApplyT(func(v HTTPIngressPath) *string { return v.PathType }).(pulumi.StringPtrOutput) } @@ -279,16 +279,16 @@ func (o HTTPIngressPathPatchOutput) Path() pulumi.StringPtrOutput { // PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is // -// done on a path element by element basis. A path element refers is the -// list of labels in the path split by the '/' separator. A request is a -// match for path p if every p is an element-wise prefix of p of the -// request path. Note that if the last element of the path is a substring -// of the last element in request path, it is not a match (e.g. /foo/bar -// matches /foo/bar/baz, but does not match /foo/barbaz). -// - ImplementationSpecific: Interpretation of the Path matching is up to -// the IngressClass. Implementations can treat this as a separate PathType -// or treat it identically to Prefix or Exact path types. -// Implementations are required to support all path types. Defaults to ImplementationSpecific. +// done on a path element by element basis. A path element refers is the +// list of labels in the path split by the '/' separator. A request is a +// match for path p if every p is an element-wise prefix of p of the +// request path. Note that if the last element of the path is a substring +// of the last element in request path, it is not a match (e.g. /foo/bar +// matches /foo/bar/baz, but does not match /foo/barbaz). +// - ImplementationSpecific: Interpretation of the Path matching is up to +// the IngressClass. Implementations can treat this as a separate PathType +// or treat it identically to Prefix or Exact path types. +// Implementations are required to support all path types. Defaults to ImplementationSpecific. func (o HTTPIngressPathPatchOutput) PathType() pulumi.StringPtrOutput { return o.ApplyT(func(v HTTPIngressPathPatch) *string { return v.PathType }).(pulumi.StringPtrOutput) } @@ -2611,10 +2611,10 @@ func (o IngressRuleOutput) ToIngressRuleOutputWithContext(ctx context.Context) I //

File modified: @@ -1104,14 +1104,14 @@ func (o PodDisruptionBudgetStatusOutput) ToPodDisruptionBudgetStatusPtrOutputWit // Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn't able to compute // -// the number of allowed disruptions. Therefore no disruptions are -// allowed and the status of the condition will be False. -// - InsufficientPods: The number of pods are either at or below the number -// required by the PodDisruptionBudget. No disruptions are -// allowed and the status of the condition will be False. -// - SufficientPods: There are more pods than required by the PodDisruptionBudget. -// The condition will be True, and the number of allowed -// disruptions are provided by the disruptionsAllowed property. +// the number of allowed disruptions. Therefore no disruptions are +// allowed and the status of the condition will be False. +// - InsufficientPods: The number of pods are either at or below the number +// required by the PodDisruptionBudget. No disruptions are +// allowed and the status of the condition will be False. +// - SufficientPods: There are more pods than required by the PodDisruptionBudget. +// The condition will be True, and the number of allowed +// disruptions are provided by the disruptionsAllowed property. func (o PodDisruptionBudgetStatusOutput) Conditions() metav1.ConditionArrayOutput { return o.ApplyT(func(v PodDisruptionBudgetStatus) []metav1.Condition { return v.Conditions }).(metav1.ConditionArrayOutput) } @@ -1172,14 +1172,14 @@ func (o PodDisruptionBudgetStatusPtrOutput) Elem() PodDisruptionBudgetStatusOutp // Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn't able to compute // -// the number of allowed disruptions. Therefore no disruptions are -// allowed and the status of the condition will be False. -// - InsufficientPods: The number of pods are either at or below the number -// required by the PodDisruptionBudget. No disruptions are -// allowed and the status of the condition will be False. -// - SufficientPods: There are more pods than required by the PodDisruptionBudget. -// The condition will be True, and the number of allowed -// disruptions are provided by the disruptionsAllowed property. +// the number of allowed disruptions. Therefore no disruptions are +// allowed and the status of the condition will be False. +// - InsufficientPods: The number of pods are either at or below the number +// required by the PodDisruptionBudget. No disruptions are +// allowed and the status of the condition will be False. +// - SufficientPods: There are more pods than required by the PodDisruptionBudget. +// The condition will be True, and the number of allowed +// disruptions are provided by the disruptionsAllowed property. func (o PodDisruptionBudgetStatusPtrOutput) Conditions() metav1.ConditionArrayOutput { return o.ApplyT(func(v *PodDisruptionBudgetStatus) []metav1.Condition { if v == nil { @@ -1392,14 +1392,14 @@ func (o PodDisruptionBudgetStatusPatchOutput) ToPodDisruptionBudgetStatusPatchPt // Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn't able to compute // -// the number of allowed disruptions. Therefore no disruptions are -// allowed and the status of the condition will be False. -// - InsufficientPods: The number of pods are either at or below the number -// required by the PodDisruptionBudget. No disruptions are -// allowed an

Unexpected changes detected: 8. See file annotations for details.