Skip to content

Commit 0423300

Browse files
authored
[trivial] strip \t in single-line descriptions (#2190)
Make helm generated template parseable with python
1 parent 580facd commit 0423300

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

config/charts/knative-operator/templates/operator.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2423,7 +2423,7 @@ spec:
24232423
anyOf:
24242424
- type: integer
24252425
- type: string
2426-
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
2426+
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
24272427
x-kubernetes-int-or-string: true
24282428
source:
24292429
description: The source configuration for Knative Eventing
@@ -4821,7 +4821,7 @@ spec:
48214821
anyOf:
48224822
- type: integer
48234823
- type: string
4824-
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
4824+
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
48254825
x-kubernetes-int-or-string: true
48264826
ingress:
48274827
description: The ingress configuration for Knative Serving

config/crd/bases/operator.knative.dev_knativeeventings.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2219,7 +2219,7 @@ spec:
22192219
anyOf:
22202220
- type: integer
22212221
- type: string
2222-
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
2222+
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
22232223
x-kubernetes-int-or-string: true
22242224
source:
22252225
description: The source configuration for Knative Eventing

config/crd/bases/operator.knative.dev_knativeservings.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2230,7 +2230,7 @@ spec:
22302230
anyOf:
22312231
- type: integer
22322232
- type: string
2233-
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
2233+
description: An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
22342234
x-kubernetes-int-or-string: true
22352235
ingress:
22362236
description: The ingress configuration for Knative Serving

0 commit comments

Comments
 (0)