Skip to content

K
k3s
Unverified Commit 48e83706 authored by Anthony Yeh's avatar Anthony Yeh
Browse files
Options

StatefulSet: Stop using `initialized` annotation in e2e tests.

Instead, use Readiness to pause and resume individual Pods to verify that the StatefulSet controller performs the right actions one at a time.
parent d2791d46
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 86 additions and 55 deletions
test/e2e/upgrades/apps/statefulset.go
View file @ 48e83706
......@@ -62,12 +62,12 @@ func (t *StatefulSetUpgradeTest) Setup(f *framework.Framework) {
t.set = framework.NewStatefulSet(ssName, ns, headlessSvcName, 2, statefulPodMounts, podMounts, labels)
t.service = framework.CreateStatefulSetService(ssName, labels)
*(t.set.Spec.Replicas) = 3
framework.SetStatefulSetInitializedAnnotation(t.set, "false")
t.tester = framework.NewStatefulSetTester(f.ClientSet)
t.tester.PauseNewPods(t.set)
By("Creating service " + headlessSvcName + " in namespace " + ns)
_, err := f.ClientSet.Core().Services(ns).Create(t.service)
Expect(err).NotTo(HaveOccurred())
t.tester = framework.NewStatefulSetTester(f.ClientSet)
By("Creating statefulset " + ssName + " in namespace " + ns)
*(t.set.Spec.Replicas) = 3
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment