forked from openstack/magnum
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync Zed with Yoga backports #164
Merged
Merged
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
In FCOS36 and later coredns started failing with loops. /etc/resolv.conf will not work with coredns (see [1]). Tested on FC35/36/37. [1]: https://github.com/coredns/coredns/blob/master/plugin/loop/README.md#troubleshooting Change-Id: I3a0700046bade7bd0b3a1b319f66b8f675f0c8fb (cherry picked from commit 037a71aaf8664a7f6a8926dceb294592d73da591) (cherry picked from commit bf99035)
This argument has been defined for containerd clusters in Magnum, and is set to the default (and only valid) value of 'remote'. Kubelet warning in 1.26: * Flag --container-runtime has been deprecated, will be removed in 1.27 as the only valid value is 'remote' Kubelet error in 1.27: * E0801 03:10:26.723998 8889 run.go:74] "command failed" err="failed to parse kubelet flag: unknown flag: --container-runtime" Change-Id: I072fab1342593941414b86e28b8a76edf2b19a6f (cherry picked from commit dc2b372)
klog args have been removed from kubernetes in 1.26, and deprecated since 1.23. kubernetes/kubernetes#112120 The argument --logtostderr has defaulted to true for a long time, so this removal on older versions should have no impact. Change-Id: I64f934a9bbc39c5e054d8a83b3f6edee061469e6 (cherry picked from commit 16baf85)
Only specify dockershim options when container runtime is not containerd. Those options were ignored in the past when using containerd but since 1.24 kubelet refuses to start. Task: 45282 Story: 2010028 Signed-off-by: Daniel Meyerholt <[email protected]> Change-Id: Ib44cc30285c8bd4219d4a45dc956696505ddd570 (cherry picked from commit f7cd292)
PodSecurityPolicy has been removed in Kubernetes v1.25 [1]. To allow Magnum to support Kubernetes v1.25 and above, PodSecurityPolicy Admission Controller has has been removed. [1] https://kubernetes.io/docs/concepts/security/pod-security-policy/ Change-Id: I0fb0c372b484275b0677114193289469ee788b84 (cherry picked from commit 1b1c212)
(cherry picked from commit d589f0f)
(cherry picked from commit cb52da1)
(cherry picked from commit c13a91e)
PodDisruptionBudget is `policy/v1` since 1.21. projectcalico/calico#4570 Change-Id: I07786095a30ae15fe856fd3966fc073267d2ae9d (cherry picked from commit 5abcab4)
Removed legacy Calico v3.3 manifest and conditional. - Change-Id: Ica52a670452e65c5ae012012895080c9c8d9abf7 (cherry picked from commit fde7f8e)
Removed Tiller support from Helm modules install kubernetes fragment. Change-Id: I81db0055ae82c64218498ae3e2a4fcc802f8d0e4 (cherry picked from commit e3aaa89)
To deploy Calico with Tigera Operator helm charts it was necessary to move Helm client install to separate script for earlier execution. Change-Id: Iab738b4120c0ac823b247b04f0cd750de0147779 (cherry picked from commit b6e2aa8)
* Renames calico script to match the version it was intended for: 3.21. * Match calico_tag 3.26.* with the new manifest. All other versions will continue to use manifest intended for 3.21.* * Calico manifest for 3.26[1] is tested for K8s versions v1.24 through v1.28[2]. [1] https://raw.githubusercontent.com/projectcalico/calico/v3.26.4/manifests/calico.yaml [2] https://docs.tigera.io/calico/3.26/getting-started/kubernetes/requirements Change-Id: I548e831c13be9b732303c945b2a7ba97a245b0df (cherry picked from commit 0fdec72)
bbezak
approved these changes
Mar 28, 2024
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.
No description provided.