Skip to content
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.20” #3260

Closed
rfranzke opened this issue Dec 2, 2020 · 3 comments
Closed

☂️-Issue for "Support for Kubernetes v1.20” #3260

rfranzke opened this issue Dec 2, 2020 · 3 comments
Assignees
Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority) topology/garden Affects Garden clusters topology/seed Affects Seed clusters topology/shoot Affects Shoot clusters

Comments

@rfranzke
Copy link
Member

rfranzke commented Dec 2, 2020

/area open-source
/kind enhancement
/priority normal
/topology garden seed shoot

Kubernetes v1.20 will be released soon, find the changelog here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md

Work has been started and is pushed to the kubernetes-v1.20 branch. There should be similar branches in the provider extension repositories in case the work has been started already.

Identified TODOs so far:

Status
completed
☑️ partly completed
🚧 in progress
to be clarified
ℹ️ interesting, but not relevant (yet)
won't fix
🚩 postponed
incomplete

gardener/gardener ➡️ #3296

gardener/gardener-extension-provider-alicloud ➡️ #204

  • ✅ Revendor gardener/gardener to allow instantiation of 1.20 Kubernetes client

gardener/gardener-extension-provider-aws ➡️ #237

  • ✅ Revendor gardener/gardener to allow instantiation of 1.20 Kubernetes client
  • ✅ Revendor gardener/cloud-provider-aws with v1.20.0 sources

gardener/gardener-extension-provider-azure ➡️ #228

gardener/gardener-extension-provider-gcp ➡️ #219

  • ✅ Revendor gardener/gardener to allow instantiation of 1.20 Kubernetes client
  • ✅ Revendor gardener/cloud-provider-gcp with v1.20.0 sources

gardener/gardener-extension-provider-openstack ➡️ #192

gardener/gardener-extension-provider-packet ➡️ #96

  • ✅ Revendor gardener/gardener to allow instantiation of 1.20 Kubernetes client

gardener/gardener-extension-provider-vsphere ➡️ #118

  • ✅ Revendor gardener/gardener to allow instantiation of 1.20 Kubernetes client
@rfranzke rfranzke added the kind/enhancement Enhancement, improvement, extension label Dec 2, 2020
@gardener-robot gardener-robot added area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related priority/normal topology/garden Affects Garden clusters topology/seed Affects Seed clusters topology/shoot Affects Shoot clusters labels Dec 2, 2020
@rfranzke rfranzke self-assigned this Dec 3, 2020
@timuthy
Copy link
Member

timuthy commented Dec 4, 2020

Disable watch caches for events, see kubernetes/kubernetes#96052

As investigated, watch cache for events.v1 was already disabled and every new release from >= 1.17 will disable the cache also for events.events.k8s.io. I don't see an action item from our side, i.e. let's move it to ℹ️?

@rfranzke
Copy link
Member Author

/cc @dguendisch @schrodit FYI :) Please prepare the execution and publishing of the conformance tests for 1.20

@rfranzke
Copy link
Member Author

/close as all related pull requests were merged

@gardener-robot gardener-robot added the priority/3 Priority (lower number equals higher priority) label Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority) topology/garden Affects Garden clusters topology/seed Affects Seed clusters topology/shoot Affects Shoot clusters
Projects
None yet
Development

No branches or pull requests

3 participants