search

gardener / gardener-extension-provider-aws

Gardener extension controller for the AWS cloud provider (https://aws.amazon.com).
https://gardener.cloud
Apache License 2.0
18 stars 96 forks source link

Bump github.com/gardener/gardener from 1.99.1 to 1.101.1 #1028

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps github.com/gardener/gardener from 1.99.1 to 1.101.1.

Release notes

Sourced from github.com/gardener/gardener's releases.

v1.101.1

[gardener/gardener]

🐛 Bug Fixes

  • [OPERATOR] Disable cloud profile field sync if Shoot is being deleted. by @​LucaBernstein #10310
  • [OPERATOR] A bug has been fixed which prevented gardenlet from creating its own seedmanagement.gardener.cloud/v1alpha1.Gardenlet resource when selfUpgrade was set in its Helm chart values (more information). by @​rfranzke #10306

Helm Charts

  • controlplane: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/controlplane:v1.101.1
  • gardenlet: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/gardenlet:v1.101.1
  • operator: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/operator:v1.101.1
  • resource-manager: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/resource-manager:v1.101.1

Docker Images

  • admission-controller: europe-docker.pkg.dev/gardener-project/releases/gardener/admission-controller:v1.101.1
  • apiserver: europe-docker.pkg.dev/gardener-project/releases/gardener/apiserver:v1.101.1
  • controller-manager: europe-docker.pkg.dev/gardener-project/releases/gardener/controller-manager:v1.101.1
  • gardenlet: europe-docker.pkg.dev/gardener-project/releases/gardener/gardenlet:v1.101.1
  • node-agent: europe-docker.pkg.dev/gardener-project/releases/gardener/node-agent:v1.101.1
  • operator: europe-docker.pkg.dev/gardener-project/releases/gardener/operator:v1.101.1
  • resource-manager: europe-docker.pkg.dev/gardener-project/releases/gardener/resource-manager:v1.101.1
  • scheduler: europe-docker.pkg.dev/gardener-project/releases/gardener/scheduler:v1.101.1

v1.101.0

[gardener/gardener]

⚠️ Breaking Changes

  • [DEVELOPER] The legacy method of providing monitoring configuration via ConfigMaps labeled with extensions.gardener.cloud/configuration=monitoring has been removed. See this instead. by @​rfranzke #10220
  • [DEVELOPER] The IPv4 addresses for the local Gardener setup was changed from 127.0.0.x to 172.18.255.x (default kind subnet) to resolve an issue on developer machines which can't use additional IP addressed from the 127.0.0.0/8 space. Please consider updating your /etc/hosts file to adjust to the the newly added addresses. Please see Deploying Gardener Locally#Accessing the Shoot Cluster for more details. by @​MartinWeindel #10019
  • [DEVELOPER] github.com/gardener/gardener/plugin/pkg/utils.ProjectForNamespaceFromLister has been deprecated and will be removed in a future release, use github.com/gardener/gardener/pkg/utils/gardener.ProjectForNamespaceFromLister instead. by @​vpnachev #10042

📰 Noteworthy

  • [DEVELOPER] Evaluate shoot.Spec.CloudProfile and shoot.Spec.CloudProfileName fields together to determine the applicable cloud profile in order to prepare for namespaced cloud profiles. by @​LucaBernstein #10093
  • [DEPENDENCY] A new field class was added to resources of the extensions.gardener.cloud API group. Together with the newly introduced predicate HasClass, it serves as a mean to split responsibilities of extension controllers for extensions belonging to different type of targets, i.e. shoot (default) or garden. Handling is backwards compatible, so that extensions are still responsible for shoot extension resources without any adjustments. If you intend to already support the reconciliation of extensions belonging to the garden class (cluster), please consider adding the ExtensionClass parameter (see here for more information). by @​timuthy #10254
  • [OPERATOR] The VPAAndHPAForAPIServer feature gate has been promoted to beta and is now turned on by default. by @​ialidzhikov #10207
  • [OPERATOR] VPA MaxAllowed is no longer hard-coded to fixed values (4/7/8 cores and 25/28G) for kube-apiserver, etcd, and prometheus. Operators must ensure sufficiently large worker pools for control plane components. For details, see this document. by @​andrerun #10208
  • [OPERATOR] The graduated CoreDNSQueryRewriting feature gate has been dropped. by @​ScheererJ #10230
  • [OPERATOR] The graduated MutableShootSpecNetworkingNodes feature gate has been dropped. by @​ScheererJ #10231
  • [USER] Use shoot.Spec.CloudProfile as the primary directive to specify the cloud profile to use. The value will by synced to the field shoot.Spec.CloudProfileName (until it is deprecated and eventually removed in the future). If no cloud profile kind is provided, it will default to CloudProfile. by @​LucaBernstein #10093

✨ New Features

  • [OPERATOR] gardener-operator is now capable of deploying gardenlets into unmanaged seed clusters. Read more about it here. by @​rfranzke #10161
  • [OPERATOR] gardener-operator is now capable of auto-updating the Helm chart reference (.spec.deployment.helm.ociRepository.ref) in seedmanagement.gardener.cloud/v1alpha1.Gardenlet resources. Read all about it here. by @​rfranzke #10218
  • [OPERATOR] gardener-operator is now capable of installing ControllerRegistration and ControllerInstallation objects in the virtual cluster based on operator.gardener.cloud/v1alpha1.Extension resources. by @​kon-angelo #10006
  • [OPERATOR] A new field Bastion was introduced to the CloudProfile. by @​hebelsan #10233

🐛 Bug Fixes

  • [OPERATOR] Valitail is now pinned to v2.2.15 (depends on glibc 2.32) by @​nickytd #10282
  • [OPERATOR] updatecacerts.service systemd unit on nodes with Debian OS does not fail anymore if /usr/local/share/ca-certificates directory is empty. by @​ScheererJ #10242

... (truncated)

Commits
  • d5a5d55 Release v1.101.1
  • 9a3acc9 Disable cloud profile field sync if shoot is being deleted (#10310)
  • d3e2058 Allow gardenlet to create its own Gardenlet resource for self-upgrades (#...
  • ec5124b Prepare next Development Cycle v1.101.1-dev
  • bd0a908 Release v1.101.0
  • 61460a0 [release-v1.101] Revert "Drop deprecated .spec.pools[].userData from `extensi...
  • 91ad4f9 [release-v1.101] Improve the SeedConditionFailing alert when nodes are rolled...
  • fbcf8a6 [release-v1.101] Pin valitail version to v2.2.15 (#10282)
  • aa54cc1 chore(deps): update golang (#10274)
  • cdbd376 fix(deps): update module golang.org/x/tools to v0.24.0 (#10273)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
gardener-robot commented 3 weeks ago

@dependabot[bot] Thank you for your contribution.

gardener-robot-ci-3 commented 3 weeks ago

Thank you @dependabot[bot] for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

dependabot[bot] commented 2 weeks ago

Superseded by #1035.