22fe385c13
Automatic merge from submit-queue test/node-e2e: Update CoreOS update disabling Previously in this saga... #25004 This disables update-engine and locksmithd with ignition instead of cloud-init so that they're really totally 100% disabled. Our ignition guy promises. Pretty much every way of disabling them with cloud-init is mildly racy. Fixes #31633 I think @vishh can say "I told you so" after the comment on https://github.com/kubernetes/kubernetes/pull/30023#discussion-diff-73431324 .. he was right, but it turns out "stop" there doesn't really work either because of the mess that is cloud-init. Fortunately, converting our cloud-init to json and calling it "ignition" works quite well 😄 Testing done: I ssh'd in and verified that yes, they're disabled. I didn't wait on the e2e tests to pass, so we'll let this PR check that. |
||
|---|---|---|
| .. | ||
| benchmark | ||
| copy-e2e-image.sh | ||
| coreos-init.json | ||
| e2e-node-jenkins.sh | ||
| gci-init.yaml | ||
| image-config.yaml | ||
| jenkins-ci.properties | ||
| jenkins-docker-validation.properties | ||
| jenkins-pull.properties | ||
| jenkins-serial.properties | ||
| template.properties | ||