Skip to content

Commit

Permalink
chore: forgot to regen
Browse files Browse the repository at this point in the history
  • Loading branch information
@lukebond
lukebond committed Nov 22, 2023
1 parent 54cdfe3 commit 32a5863
Show file tree
Hide file tree
Showing 2 changed files with 138 additions and 0 deletions.
69 changes: 69 additions & 0 deletions bootstrap/config/crd/bases/controlplane.cluster.x-k8s.io_kthreescontrolplanes.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,51 @@ spec:
limitations. NOTE: NodeDrainTimeout is different from `kubectl drain
--timeout`'
type: string
remediationStrategy:
description: The RemediationStrategy that controls how control plane
machine remediation happens.
properties:
maxRetry:
description: "MaxRetry is the Max number of retries while attempting
to remediate an unhealthy machine. A retry happens when a machine
that was created as a replacement for an unhealthy machine also
fails. For example, given a control plane with three machines
M1, M2, M3: \n M1 become unhealthy; remediation happens, and
M1-1 is created as a replacement. If M1-1 (replacement of M1)
has problems while bootstrapping it will become unhealthy, and
then be remediated; such operation is considered a retry, remediation-retry
#1. If M1-2 (replacement of M1-1) becomes unhealthy, remediation-retry
#2 will happen, etc. \n A retry could happen only after RetryPeriod
from the previous retry. If a machine is marked as unhealthy
after MinHealthyPeriod from the previous remediation expired,
this is not considered a retry anymore because the new issue
is assumed unrelated from the previous one. \n If not set, the
remedation will be retried infinitely."
format: int32
type: integer
minHealthyPeriod:
description: "MinHealthyPeriod defines the duration after which
KCP will consider any failure to a machine unrelated from the
previous one. In this case the remediation is not considered
a retry anymore, and thus the retry counter restarts from 0.
For example, assuming MinHealthyPeriod is set to 1h (default)
\n M1 become unhealthy; remediation happens, and M1-1 is created
as a replacement. If M1-1 (replacement of M1) has problems within
the 1hr after the creation, also this machine will be remediated
and this operation is considered a retry - a problem related
to the original issue happened to M1 -. \n If instead the problem
on M1-1 is happening after MinHealthyPeriod expired, e.g. four
days after m1-1 has been created as a remediation of M1, the
problem on M1-1 is considered unrelated to the original issue
happened to M1. \n If not set, this value is defaulted to 1h."
type: string
retryPeriod:
description: "RetryPeriod is the duration that KCP should wait
before remediating a machine being created as a replacement
for an unhealthy machine (a retry). \n If not set, a retry will
happen immediately."
type: string
type: object
replicas:
description: Number of desired machines. Defaults to 1. When stacked
etcd is used only odd numbers are permitted, as per [etcd best practice](https://etcd.io/docs/v3.3.12/faq/#why-an-odd-number-of-cluster-members).
Expand Down Expand Up @@ -403,6 +448,30 @@ spec:
description: Initialized denotes whether or not the k3s server is
initialized.
type: boolean
lastRemediation:
description: LastRemediation stores info about last remediation performed.
properties:
machine:
description: Machine is the machine name of the latest machine
being remediated.
type: string
retryCount:
description: RetryCount used to keep track of remediation retry
for the last remediated machine. A retry happens when a machine
that was created as a replacement for an unhealthy machine also
fails.
format: int32
type: integer
timestamp:
description: Timestamp is when last remediation happened. It is
represented in RFC3339 form and is in UTC.
format: date-time
type: string
required:
- machine
- retryCount
- timestamp
type: object
observedGeneration:
description: ObservedGeneration is the latest generation observed
by the controller.
Expand Down
69 changes: 69 additions & 0 deletions controlplane/config/crd/bases/controlplane.cluster.x-k8s.io_kthreescontrolplanes.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,51 @@ spec:
limitations. NOTE: NodeDrainTimeout is different from `kubectl drain
--timeout`'
type: string
remediationStrategy:
description: The RemediationStrategy that controls how control plane
machine remediation happens.
properties:
maxRetry:
description: "MaxRetry is the Max number of retries while attempting
to remediate an unhealthy machine. A retry happens when a machine
that was created as a replacement for an unhealthy machine also
fails. For example, given a control plane with three machines
M1, M2, M3: \n M1 become unhealthy; remediation happens, and
M1-1 is created as a replacement. If M1-1 (replacement of M1)
has problems while bootstrapping it will become unhealthy, and
then be remediated; such operation is considered a retry, remediation-retry
#1. If M1-2 (replacement of M1-1) becomes unhealthy, remediation-retry
#2 will happen, etc. \n A retry could happen only after RetryPeriod
from the previous retry. If a machine is marked as unhealthy
after MinHealthyPeriod from the previous remediation expired,
this is not considered a retry anymore because the new issue
is assumed unrelated from the previous one. \n If not set, the
remedation will be retried infinitely."
format: int32
type: integer
minHealthyPeriod:
description: "MinHealthyPeriod defines the duration after which
KCP will consider any failure to a machine unrelated from the
previous one. In this case the remediation is not considered
a retry anymore, and thus the retry counter restarts from 0.
For example, assuming MinHealthyPeriod is set to 1h (default)
\n M1 become unhealthy; remediation happens, and M1-1 is created
as a replacement. If M1-1 (replacement of M1) has problems within
the 1hr after the creation, also this machine will be remediated
and this operation is considered a retry - a problem related
to the original issue happened to M1 -. \n If instead the problem
on M1-1 is happening after MinHealthyPeriod expired, e.g. four
days after m1-1 has been created as a remediation of M1, the
problem on M1-1 is considered unrelated to the original issue
happened to M1. \n If not set, this value is defaulted to 1h."
type: string
retryPeriod:
description: "RetryPeriod is the duration that KCP should wait
before remediating a machine being created as a replacement
for an unhealthy machine (a retry). \n If not set, a retry will
happen immediately."
type: string
type: object
replicas:
description: Number of desired machines. Defaults to 1. When stacked
etcd is used only odd numbers are permitted, as per [etcd best practice](https://etcd.io/docs/v3.3.12/faq/#why-an-odd-number-of-cluster-members).
Expand Down Expand Up @@ -403,6 +448,30 @@ spec:
description: Initialized denotes whether or not the k3s server is
initialized.
type: boolean
lastRemediation:
description: LastRemediation stores info about last remediation performed.
properties:
machine:
description: Machine is the machine name of the latest machine
being remediated.
type: string
retryCount:
description: RetryCount used to keep track of remediation retry
for the last remediated machine. A retry happens when a machine
that was created as a replacement for an unhealthy machine also
fails.
format: int32
type: integer
timestamp:
description: Timestamp is when last remediation happened. It is
represented in RFC3339 form and is in UTC.
format: date-time
type: string
required:
- machine
- retryCount
- timestamp
type: object
observedGeneration:
description: ObservedGeneration is the latest generation observed
by the controller.
Expand Down

0 comments on commit 32a5863

Please sign in to comment.