cilium/charts: set system-{node,cluster}-critical priorityClass for k8s >= 1.17 #12151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Performing a "greater than 16" causes the logic to be true when the cluster is running with a minor version set to "16+" which is incorrect. With this commit, the priorityClass will only be set when the clusters are "greater or equal than 17". Fixes: ce99a99 ("Set priorityClassName outside kube-system in k8s 1.17+") Signed-off-by: André Martins <andre@cilium.io>
aanm
added
release-note/bug
tgraf
approved these changes
Jun 17, 2020
rolinh
approved these changes
Jun 17, 2020
|
test-me-please |
joestringer
approved these changes
Jun 18, 2020
michi-covalent
approved these changes
Jun 18, 2020
|
test-missed-k8s |
|
all known flakes merging |
maintainer-s-little-helper
bot
moved this from Needs backport from master
to Backport pending to v1.8
in 1.8.0
maintainer-s-little-helper
bot
moved this from Backport pending to v1.8
to Backport done to v1.8
in 1.8.0
maintainer-s-little-helper
bot
moved this from Backport pending to v1.8
to Backport done to v1.8
in 1.8.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Performing a "greater than 16" causes the logic to be true when the
cluster is running with a minor version set to "16+" which is incorrect.
With this commit, the priorityClass will only be set when the clusters
are "greater or equal than 17".
Fixes: ce99a99 ("Set priorityClassName outside kube-system in k8s 1.17+")
Signed-off-by: André Martins andre@cilium.io