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

bump dependencies #1202

Merged
merged 29 commits into from
Sep 18, 2023
Merged

bump dependencies #1202

merged 29 commits into from
Sep 18, 2023

Conversation

Diaphteiros
Copy link
Contributor

Release note:

Default k8s versions and machine image versions have been upgraded.
Upgrade Gardener extension os-gardenlinux to `v0.20.0`
Upgrade Gardener extension suse-chost to `v1.22.0`
Upgrade Gardener extension os-ubuntu to `v1.22.0`
Upgrade Gardener dns-controller-manager to `v0.15.8`
Upgrade Gardener extension provider-gcp to `v1.32.0`
Upgrade Gardener extension provider-aws to `v1.46.0`
Upgrade Gardener extension provider-openstack to `v1.36.0`
Upgrade Gardener extension provider-azure to `v1.38.1`
Upgrade Gardener extension networking-calico to `v1.36.0`
Upgrade Gardener extension runtime-gvisor to `v0.11.0`
Upgrade Gardener extension provider-vsphere to `v0.31.2`
Upgrade Gardener extension shoot-dns-service to `v1.38.1`
Upgrade Gardener cert-manager to `v0.11.0`
Upgrade Gardener extension shoot-cert-service to `v1.36.0`
Upgrade Gardener to `v1.67.2`
Upgrade Gardener Dashboard to `v1.68.2`
⚠️ Since Gardener now automatically deploys `NetworkPolicy` resources into the `gardener` namespace of a seed - which messes up the communication on the base cluster - the network policies deployed by garden-setup itself had to be modified: if the network policies are activated, garden-setup will now deploy an additional `allow-all-ingress` policy, allowing all ingress traffic in the base cluster's `garden` namespace. If the network policies are deactivated, garden-setup instead uses an `allow-all` policy that simply allows all egress and ingress traffic in the `garden` namespace. There are no changes required, unless you are actively working with network policies in the base cluster's `garden` namespace.
⚠️ Due to some changes in Gardener's certificate handling, the ingress certificate changed slightly: instead of just using the wildcard ingress domain as Common Name, it now uses the dashboard's domain as CN and has the wildcard ingress domain configured as SAN. There are no changes required, unless you are interacting with the ingress certificate in some way and rely on its CN value.

gardener-robot-ci-1 and others added 29 commits April 21, 2023 10:48
)

from v1.32.1 to v1.33.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
* Upgrade github_com_gardener_dashboard

from 1.67.0 to 1.68.2
from v0.26.0 to v0.27.0

Co-authored-by: gardener-robot-ci-2 <gardener.ci.user2@gmail.com>
from v1.31.2 to v1.32.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
)

from v1.30.1 to v1.31.0

Co-authored-by: gardener-robot-ci-1 <gardener.ci.user@gmail.com>
from v0.10.4 to v0.11.0

Co-authored-by: gardener-robot-ci-1 <gardener.ci.user@gmail.com>
from v1.32.1 to v1.38.1

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
from v0.9.1 to v0.11.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
from v1.32.0 to v1.36.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
from v1.35.0 to v1.38.1

Co-authored-by: gardener-robot-ci-1 <gardener.ci.user@gmail.com>
)

from v1.33.0 to v1.36.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
from v1.29.0 to v1.32.0

Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
from v0.15.2 to v0.15.8

Co-authored-by: gardener-robot-ci-1 <gardener.ci.user@gmail.com>
…0->v1.22.0] (#1124)

* upgrade etcd and use custom image

* Upgrade github_com_gardener_gardener-extension-os-ubuntu

from v1.21.0 to v1.22.0

---------

Co-authored-by: Johannes Aubart <johannes.aubart@sap.com>
….21.0->v1.22.0] (#1110)

* upgrade etcd and use custom image

* Upgrade github_com_gardener_gardener-extension-os-suse-chost

from v1.21.0 to v1.22.0

---------

Co-authored-by: Johannes Aubart <johannes.aubart@sap.com>
Co-authored-by: gardener-robot-ci-3 <gardener.ci.user3@gmail.com>
…0.19.0->v0.20.0] (#1107)

* upgrade etcd and use custom image

* Upgrade github_com_gardener_gardener-extension-os-gardenlinux

from v0.19.0 to v0.20.0

---------

Co-authored-by: Johannes Aubart <johannes.aubart@sap.com>
Co-authored-by: gardener-robot-ci-2 <gardener.ci.user2@gmail.com>
@Diaphteiros Diaphteiros requested a review from a team as a code owner September 18, 2023 08:49
@gardener-robot gardener-robot added needs/review Needs review size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) needs/second-opinion Needs second review by someone else labels Sep 18, 2023
@Diaphteiros Diaphteiros merged commit a4ded18 into master Sep 18, 2023
1 check passed
@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs/review Needs review needs/second-opinion Needs second review by someone else size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants