Disable EventedPLEG featuregate in techpreview #1483
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In combination with openshift/machine-config-operator#3688, this was causing an issue in TechPreview clusters.
Myself and @sergiordlr both observed that, when enabled in the cluster by the machine-config-operator, this feature gate got passed through to the Kubelet and weird interactions were happening between kubelet and crio causing odd behaviour and duplicate containers/bind address issues.
In my testing, disabling this feature lead to a healthy cluster within 3688. In these test runs the tech preview clusters bootstrapped correctly where previously they had been failing to bootstrap, this run was against a commit that deliberately excluded passing
EventedPLEGto the kubelet.Discussion in slack here and here
If we exclude the feature for now, once 3688 has merged, we can reintroduce this and test via a PR to cluster-config-operator to make sure track any issues being caused. Currently, because MCO was not up to date, it had not been able to be tested in the cluster pre-merge.
CC @harche @sairameshv