kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

make crds

This commit is contained in:
John Gardiner Myers 2020-01-05 17:54:45 -08:00
parent c95a43c026
commit b8e665018c
2 changed files with 40 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
k8s/crds/kops.k8s.io_clusters.yaml
View File

@ -2889,6 +2889,19 @@ spec:
description: RollingUpdate defines the default rolling-update settings
for instance groups
properties:
maxSurge:
anyOf:
- type: string
- type: integer
description: 'MaxSurge is the maximum number of extra nodes that
can be created during the update. The value can be an absolute
number (for example 5) or a percentage of desired machines (for
example 10%). The absolute number is calculated from a percentage
by rounding up. A value of 0 for both this and MaxUnavailable
disables rolling updates. Defaults to 0. Example: when this is
set to 30%, the InstanceGroup can be scaled up immediately when
the rolling update starts, such that the total number of old and
new nodes do not exceed 130% of desired nodes.'
maxUnavailable:
anyOf:
- type: string
@ -2897,12 +2910,13 @@ spec:
can be unavailable during the update. The value can be an absolute
number (for example 5) or a percentage of desired nodes (for example
10%). The absolute number is calculated from a percentage by rounding
down. A value of 0 disables rolling updates. Defaults to 1. Example:
when this is set to 30%, the InstanceGroup can be scaled down
to 70% of desired nodes immediately when the rolling update starts.
Once new nodes are ready, more old nodes can be drained, ensuring
that the total number of nodes available at all times during the
update is at least 70% of desired nodes.'
down. A value of 0 for both this and MaxSurge disables rolling
updates. Defaults to 1 if MaxSurge is 0, otherwise defaults to
0. Example: when this is set to 30%, the InstanceGroup can be
scaled down to 70% of desired nodes immediately when the rolling
update starts. Once new nodes are ready, more old nodes can be
drained, ensuring that the total number of nodes available at
all times during the update is at least 70% of desired nodes.'
type: object
secretStore:
description: SecretStore is the VFS path to where secrets are stored

26
k8s/crds/kops.k8s.io_instancegroups.yaml
View File

@ -627,6 +627,19 @@ spec:
rollingUpdate:
description: RollingUpdate defines the rolling-update behavior
properties:
maxSurge:
anyOf:
- type: string
- type: integer
description: 'MaxSurge is the maximum number of extra nodes that
can be created during the update. The value can be an absolute
number (for example 5) or a percentage of desired machines (for
example 10%). The absolute number is calculated from a percentage
by rounding up. A value of 0 for both this and MaxUnavailable
disables rolling updates. Defaults to 0. Example: when this is
set to 30%, the InstanceGroup can be scaled up immediately when
the rolling update starts, such that the total number of old and
new nodes do not exceed 130% of desired nodes.'
maxUnavailable:
anyOf:
- type: string
@ -635,12 +648,13 @@ spec:
can be unavailable during the update. The value can be an absolute
number (for example 5) or a percentage of desired nodes (for example
10%). The absolute number is calculated from a percentage by rounding
down. A value of 0 disables rolling updates. Defaults to 1. Example:
when this is set to 30%, the InstanceGroup can be scaled down
to 70% of desired nodes immediately when the rolling update starts.
Once new nodes are ready, more old nodes can be drained, ensuring
that the total number of nodes available at all times during the
update is at least 70% of desired nodes.'
down. A value of 0 for both this and MaxSurge disables rolling
updates. Defaults to 1 if MaxSurge is 0, otherwise defaults to
0. Example: when this is set to 30%, the InstanceGroup can be
scaled down to 70% of desired nodes immediately when the rolling
update starts. Once new nodes are ready, more old nodes can be
drained, ensuring that the total number of nodes available at
all times during the update is at least 70% of desired nodes.'
type: object
rootVolumeDeleteOnTermination:
description: 'RootVolumeDeleteOnTermination configures root volume retention