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

chore(dependabot): bump github.com/gardener/gardener from 1.110.1 to 1.111.1 in the gardener group #998

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 3, 2025

Bumps the gardener group with 1 update: github.com/gardener/gardener.

Updates github.com/gardener/gardener from 1.110.1 to 1.111.1

Release notes

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

v1.111.1

[gardener/gardener]

✨ New Features

  • [DEVELOPER] A wrapper function for OperatingSystemConfig provisioning bash script has been implemented. Using the wrapper ensures that the script exits early in case it has been executed successfully before. by @​oliver-goetz #11257

🏃 Others

  • [DEPENDENCY] The gardener/dashboard image has been updated to 1.79.1. Release Notes by @​gardener-ci-robot #11262
  • [OPERATOR] An issue has been fixed that caused the garden reconciliation to stop when structured authentication was used in combination with the gardener-dashboard oidcConfig. by @​timuthy #11233
  • [DEVELOPER] testing framework: The RootPodExecutor no longer requires output from command execution to interpret the command execution as successful. by @​ialidzhikov #11253

Helm Charts

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

Docker Images

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

v1.111.0

[gardener/gardener]

⚠️ Breaking Changes

  • [OPERATOR] The OperatorConfiguration changed incompatibly: extensionRequired was renamed to extensionRequiredRuntime. by @​timuthy #11001

  • [OPERATOR] The ShootManagedIssuer feature gate was removed. Enablement of the feature is now dependent on the existence of a secret in the garden namespace labeled with gardener.cloud/role: shoot-service-account-issuer. by @​dimityrmirchev #11078

  • [OPERATOR] The ShootForceDeletion feature gate has been graduated to GA and is locked to true. by @​shafeeqes #11107

  • [OPERATOR] This change applies to IPv4 clusters only.
    Gardener uses the CIDR range of 240.0.0.0/8 which is reserved as per IANA db to map the cluster ip of the kubernetes api-server in the seed to a different network range before exposing it to the shoot in the kubernetes service. This frees up address space in the shoot and removes potential clashes with shoot workload ips.

    Seed operators need to check if any of the following properties collide with the 240.0.0.0/8 range:

    spec:  
      networks:  
        pods: < check here >  
        nodes: < check here >  
        services: < check here >  
        shootDefaults:  
          pods: < check here >  
          nodes: < check here >  
          services: < check here >  
    

    by @​domdom82 #10949

... (truncated)

Commits
  • 14dbecb Release v1.111.1
  • 323e637 chore(deps): update dependency gardener/dashboard to v1.79.1 (#11262)
  • e2af210 [release-v1.111] Create a wrapper for OperatingSystemConfig provisioning ba...
  • 995b550 RootPodExecutor: Do not require output from command execution (#11253)
  • 0fd12b3 Fix nil pointer deref in Structured Authn (#11233)
  • 0ca15eb Prepare next Development Cycle v1.111.1-dev
  • 37ae9bf Release v1.111.0
  • 8fda81b chore(deps): update registry.k8s.io/ingress-nginx/controller-chroot docker ta...
  • fa1658e Consider machine image name while calculating list of valid image (#11220)
  • 822c574 Fix TM test Shoot container runtime testing (#11219)
  • 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the gardener group with 1 update: [github.com/gardener/gardener](https://github.com/gardener/gardener).


Updates `github.com/gardener/gardener` from 1.110.1 to 1.111.1
- [Release notes](https://github.com/gardener/gardener/releases)
- [Commits](gardener/gardener@v1.110.1...v1.111.1)

---
updated-dependencies:
- dependency-name: github.com/gardener/gardener
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: gardener
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner February 3, 2025 06:32
@dependabot dependabot bot added area/dependency Issues or PRs related to dependency changes go labels Feb 3, 2025
@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes cla: yes Indicates the PR's author has signed the CLA. go size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant