You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api/core/v1beta2/machineset_types.go
+23Lines changed: 23 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,29 @@ const (
33
33
// MachineSetFinalizer is the finalizer used by the MachineSet controller to
34
34
// ensure ordered cleanup of corresponding Machines when a Machineset is being deleted.
35
35
MachineSetFinalizer="cluster.x-k8s.io/machineset"
36
+
37
+
// MachineSetMoveMachinesToMachineSetAnnotation is an internal annotation added by the MD controller to the oldMS
38
+
// when it should scale down by moving machines that can be updated in-place to the newMS instead of deleting them.
39
+
// The annotation value is the newMS name.
40
+
// Note: This annotation is used in pair with MachineSetReceiveMachinesFromMachineSetsAnnotation to perform a two-ways check before moving a machine from oldMS to newMS:
41
+
//
42
+
// "oldMS must have: move to newMS" and "newMS must have: receive replicas from oldMS"
// MachineSetReceiveMachinesFromMachineSetsAnnotation is an internal annotation added by the MD controller to the newMS
46
+
// when it should receive replicas from oldMSs as a first step of an in-place upgrade operation
47
+
// The annotation value is a comma separated list of oldMSs.
48
+
// Note: This annotation is used in pair with MachineSetMoveMachinesToMachineSetAnnotation to perform a two-ways check before moving a machine from oldMS to newMS:
49
+
//
50
+
// "oldMS must have: move to newMS" and "newMS must have: receive replicas from oldMS"
Copy file name to clipboardExpand all lines: docs/book/src/reference/api/labels-and-annotations.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,29 @@
58
58
| topology.cluster.x-k8s.io/dry-run | It is an annotation that gets set on objects by the topology controller only during a server side dry run apply operation. It is used for validating update webhooks for objects which get updated by template rotation (e.g. InfrastructureMachineTemplate). When the annotation is set and the admission request is a dry run, the webhook should deny validation due to immutability. By that the request will succeed (without any changes to the actual object because it is a dry run) and the topology controller will receive the resulting object. | Cluster API | Template rotation objects |
59
59
| topology.cluster.x-k8s.io/hold-upgrade-sequence | It can be used to hold the entire MachineDeployment upgrade sequence. If the annotation is set on a MachineDeployment topology in Cluster.spec.topology.workers, the Kubernetes upgrade for this MachineDeployment topology and all subsequent ones is deferred. | Cluster API | MachineDeployments in Cluster.topology |
60
60
| topology.cluster.x-k8s.io/upgrade-concurrency | It can be used to configure the maximum concurrency while upgrading MachineDeployments of a classy Cluster. It is set as a top level annotation on the Cluster object. The value should be >= 1. If unspecified the upgrade concurrency will default to 1. | Cluster API | Clusters |
61
-
| topology.internal.cluster.x-k8s.io/upgrade-step | This is an annotation used by CAPI internally to track upgrade steps. Name, meaning and semantic of the annotation can change anytime and it should not be used outside of CAPI controllers. | Cluster API | Clusters |
62
61
| unsafe.topology.cluster.x-k8s.io/disable-update-class-name-check | It can be used to disable the webhook check on update that disallows a pre-existing Cluster to be populated with Topology information and Class. | User | Clusters |
63
62
| unsafe.topology.cluster.x-k8s.io/disable-update-version-check | It can be used to disable the webhook checks on update that disallows updating the .topology.spec.version on certain conditions. | User | Clusters |
63
+
64
+
65
+
# Internal Annotations
66
+
67
+
Following annotation are used by CAPI internally.
68
+
69
+
<asideclass="note warning">
70
+
71
+
<h1>Internal annotations should not be used outside CAPI controllers</h1>
72
+
73
+
Name, meaning and semantic of internal annotations can change anytime.
74
+
75
+
Users must not change or remove internal annotation on CAPI resources, because this can lead to issues or unexpected behaviour of the system.
| in-place-updates.internal.cluster.x-k8s.io/acknowledge-move | This annotation is added by the MD controller to a MachineSet when it acknowledges a machine pending acknowledge after being moved from an oldMS | MachineSet |
82
+
| in-place-updates.internal.cluster.x-k8s.io/move-machines-to-machineset | This annotation is added by the MD controller to the oldMS when it should scale down by moving machines that can be updated in-place to the newMS instead of deleting them. | MachineSet |
83
+
| in-place-updates.internal.cluster.x-k8s.io/pending-acknowledge-move | This annotation is by the MS controller to a machine when being moved from the oldMS to the newMS | Machine |
84
+
| in-place-updates.internal.cluster.x-k8s.io/receive-machines-from-machinesets | This annotation is added by the MD controller to the newMS when it should receive replicas from an oldMS | MachineSet |
85
+
| in-place-updates.internal.cluster.x-k8s.io/update-in-progress | This annotation is added to machines by the controller owning the Machine when in-place update is started | Machine |
86
+
| topology.internal.cluster.x-k8s.io/upgrade-step | This is an annotation used by the topology controller to a cluster to track upgrade steps. | Clusters |
0 commit comments