-
Notifications
You must be signed in to change notification settings - Fork 450
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
☂️-Issue for "Support for Kubernetes v1.25” #6567
Comments
/assign |
With 1.25 the folks (@dkistner and @kon-angelo) wanted to try out the upstream CCM - ref gardener/gardener-extension-provider-aws#577. |
@dkistner @kon-angelo Can this switch to the OOT CCM also be done later (after 1.25 is already supported) so that we get rid this dependency on the tasks? |
The argument in the past was to not perform the upgrade in the middle of kubernetes releases so that we don't have any weird or unexpected behaviour due to the transition. In general OOT should be a superset of the behavior of the in-tree CCM. In practice if we go though with upgrade in-tree now, we would need to verify one extra transition (in-tree 1.25 -> oot 1.25) in addition to the others, but I do not think it would be that much extra effort. |
OK, cc @shafeeqes. Let's see how it goes then and talk about this once we have finished the other items from above list. |
I was actually thinking about this topic and I guess it will be best if you @dkistner and @kon-angelo can handle this with a feature gate so we can decouple it from the 1.25 topic. At the end, our final goal is a controlled rollout and a feature gate should do the trick. WDYT? |
@ialidzhikov I think that is a great idea. If my previous comment was not clear as to its intentions, I agree that we can and should decouple it from gardener's 1.25 support and doing it via feature gate could be a good way to introduce the change. |
/close |
@shafeeqes: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Shouldn't we keep it open for
? Or is it tracked somewhere else? |
Opened a new issue. We can keep this closed. |
We need to use cluster autoscaler v1.25 for 1.25 Shoots,
/assign @himanshu-kun @rishabh-11 |
/close |
@shafeeqes: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/area open-source
/kind enhancement
/priority 3
/topology garden seed shoot
Kubernetes v1.25 has been released, find the changelog here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md
Work can be started and pushed to the
kubernetes-v1.25
branch. There should be similar branches in the provider extension repositories in case the work has been started already.Note: Seeds do not support
v1.25
yet (Tracked separately in #6893 ) because of:[Feature] Update API versions for Cronjobs and PDBs etcd-druid#429HorizontalPodAutoscaler
hvpa-controller#104Tasks
Hyperkube
hyperkube
: https://github.com/gardener/hyperkube/releases/tag/v1.25.0Gardener
gardener
: Support for Kubernetes v1.25 #6638PodSecurityPolicy
usage / move toPodSecurity
#5250README.md
anddocs/usage/supported_k8s_versions.md
no changes
PodDisruptionBudget
policy/v1
HorizontalPodAutoscaler
autoscaling/v2
k8s.io/*
tov0.25
,sigs.k8s.io/controller-runtime
tov0.13
#6668v1.56.0
Cloud Controller Managers
cloud-provider-aws
legacy-cloud-providers
and createrelease-v1.25
branch from it (update container images and revendor latest Kubernetes patch):v1.25.2
release-v1.24
branch (update container images and revendor latest Kubernetes patch):v1.24.6
release-v1.23
branch (update container images and revendor latest Kubernetes patch):v1.23.12
release-v1.22
branch (update container images and revendor latest Kubernetes patch):v1.22.15
cloud-provider-azure
release-v1.22
branch (update container images and revendor latest Kubernetes patch):v1.22.15
cloud-provider-gcp
legacy-cloud-providers
and createrelease-v1.25
branch from it (update container images and revendor latest Kubernetes patch):v1.25.2
release-v1.24
branch (update container images and revendor latest Kubernetes patch):v1.24.6
release-v1.23
branch (update container images and revendor latest Kubernetes patch):v1.23.12
release-v1.22
branch (update container images and revendor latest Kubernetes patch):v1.22.15
Provider Extensions
provider-alicloud
: Support for Kubernetes v1.25 gardener-extension-provider-alicloud#537machine-controller-manager
andmachine-controller-manager-provider-alicloud
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-alicloud#534README.md
with support for 1.25v1.41.0
provider-aws
: Support for Kubernetes v1.25 gardener-extension-provider-aws#624machine-controller-manager
andmachine-controller-manager-provider-aws
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-aws#609README.md
with support for 1.25cloud-controller-manager
imagesv1.39.0
provider-azure
: Support for Kubernetes v1.25 gardener-extension-provider-azure#575machine-controller-manager
andmachine-controller-manager-provider-azure
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-azure#572README.md
with support for 1.25cloud-controller-manager
imagesv1.31.0
provider-gcp
: Support for Kubernetes v1.25 gardener-extension-provider-gcp#498machine-controller-manager
andmachine-controller-manager-provider-gcp
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-gcp#496README.md
with support for 1.25cloud-controller-manager
imagesprovider-openstack
: Support for Kubernetes v1.25 gardener-extension-provider-openstack#502machine-controller-manager
andmachine-controller-manager-provider-openstack
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-openstack#495README.md
with support for 1.25cloud-controller-manager
imagesv1.29.0
provider-vsphere
: Support for Kubernetes v1.25 gardener-attic/gardener-extension-provider-vsphere#305machine-controller-manager
andmachine-controller-manager-provider-vsphere
gardener/gardener
with support for 1.25 client creationgardener@1.56.0-dev
and Upgrade k8s dependencies and controller-runtime gardener-attic/gardener-extension-provider-vsphere#303README.md
with support for 1.25v0.20.0
provider-equinix-metal
: Support for Kubernetes v1.25 gardener-extension-provider-equinix-metal#232machine-controller-manager
andmachine-controller-manager-provider-equinix-metal
gardener/gardener
with support for 1.25 client creationgardener@1.56.0
and Upgrade k8s dependencies and controller-runtime gardener-extension-provider-equinix-metal#230README.md
with support for 1.25v2.5.0
Networking Extensions
networking-calico
: HandlePodDisuptionBudget
policy/v1
and Vendorgardener@1.54
(For changes in the PSP helper function to support k8s v1.25) > Vendorgardener@1.54.0
and HandlePodDisruptionBudget
policy/v1
gardener-extension-networking-calico#210v1.27.0
networking-cilium
: HandlePodDisuptionBudget
policy/v1
and Vendorgardener@1.54
(For changes in the PSP helper function to support k8s v1.25) > Vendorgardener@1.54.0
and HandlePodDisruptionBudget
policy/v1
gardener-extension-networking-cilium#126v1.17.0
Machine Controller Manager
PodDisruptionBudget
policy/v1
> HandlePodDisruptionBudget
policy/v1
machine-controller-manager#744v0.47.0
Shoot Extensions
extensions-networking-problem-detector
: HandlePodDisuptionBudget
policy/v1
and Vendorgardener@1.54
(For changes in the PSP helper function to support k8s v1.25) > Vendorgardener@1.54.0
and HandlePodDisruptionBudget
policy/v1
gardener-extension-shoot-networking-problemdetector#29v0.7.0
extensions-networking-filter
: HandlePodDisuptionBudget
policy/v1
and Vendorgardener@1.54
(For changes in the PSP helper function to support k8s v1.25) > Vendorgardener@1.54.0
and HandlePodDisruptionBudget
policy/v1
gardener-extension-shoot-networking-filter#32v0.7.0
gardener-extension-shoot-oidc-service
: HandlePodDisuptionBudget
policy/v1
and Vendorgardener@1.54
> Vendorgardener@1.54.0
and Handle PodDisruptionBudgetpolicy/v1
gardener-extension-shoot-oidc-service#64v0.10.0
extensions-shoot-dns-service
: HandlePodDisuptionBudget
policy/v1
HandlePodDisruptionBudget
policy/v1
gardener-extension-shoot-dns-service#161v1.25.0
The text was updated successfully, but these errors were encountered: