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
test-infrastructure-no-race: $(SETUP_ENVTEST)## Run unit and integration tests with no race detector for docker infrastructure provider
951
+
# Note: Fuzz tests are not executed with race detector because they would just time out.
952
+
# To achieve that, all files with fuzz tests have the "!race" build tag, to still run fuzz tests
953
+
# we have an additional `go test` run that focuses on "TestFuzzyConversion".
954
+
cd test/infrastructure; KUBEBUILDER_ASSETS="$(KUBEBUILDER_ASSETS)" go test ./... $(TEST_ARGS)
955
+
949
956
.PHONY: test-infrastructure-conversions
950
957
test-infrastructure-conversions: $(SETUP_ENVTEST)## Run conversions test for docker infrastructure provider
951
958
cd test/infrastructure; KUBEBUILDER_ASSETS="$(KUBEBUILDER_ASSETS)" go test -run "^TestFuzzyConversion$$" ./... $(TEST_ARGS)
@@ -956,7 +963,7 @@ test-infrastructure-verbose: ## Run unit and integration tests with race detecto
956
963
957
964
.PHONY: test-infrastructure-junit
958
965
test-infrastructure-junit: $(SETUP_ENVTEST)$(GOTESTSUM)## Run unit and integration tests with race detector and generate a junit report for docker infrastructure provider
959
-
cd test/infrastructure;set +o errexit; (KUBEBUILDER_ASSETS="$(KUBEBUILDER_ASSETS)" go test -json ./... $(TEST_ARGS);echo$$?>$(ARTIFACTS)/junit.infra_docker.exitcode) | tee $(ARTIFACTS)/junit.infra_docker.stdout
966
+
cd test/infrastructure;set +o errexit; (KUBEBUILDER_ASSETS="$(KUBEBUILDER_ASSETS)" go test -race -json ./... $(TEST_ARGS);echo$$?>$(ARTIFACTS)/junit.infra_docker.exitcode) | tee $(ARTIFACTS)/junit.infra_docker.stdout
cd test/infrastructure;set +o errexit; (KUBEBUILDER_ASSETS="$(KUBEBUILDER_ASSETS)" go test -run "^TestFuzzyConversion$$" -json ./... $(TEST_ARGS);echo$$?>$(ARTIFACTS)/junit-fuzz.infra_docker.exitcode) | tee $(ARTIFACTS)/junit-fuzz.infra_docker.stdout
// +kubebuilder:validation:XValidation:rule="!(self in ['Ready','Available','HealthCheckSucceeded','OwnerRemediated','ExternallyRemediated'])",message="type must not be one of: Ready, Available, HealthCheckSucceeded, OwnerRemediated, ExternallyRemediated"
256
+
// +required
257
+
Typestring`json:"type,omitempty"`
258
+
259
+
// status of the condition, one of True, False, Unknown.
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"
0 commit comments