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 github.com/gardener/gardener from 1.110.3 to 1.111.1 #175

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 30, 2025

Bumps github.com/gardener/gardener from 1.110.3 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 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)

Bumps [github.com/gardener/gardener](https://github.com/gardener/gardener) from 1.110.3 to 1.111.1.
- [Release notes](https://github.com/gardener/gardener/releases)
- [Commits](gardener/gardener@v1.110.3...v1.111.1)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jan 30, 2025
@dependabot dependabot bot requested review from a team as code owners January 30, 2025 02:00
@gardener-robot
Copy link

@dependabot[bot] Thank you for your contribution.

@gardener-robot gardener-robot added needs/review Needs review size/m Size of pull request is medium (see gardener-robot robot/bots/size.py) labels Jan 30, 2025
@gardener-robot-ci-3
Copy link
Contributor

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.

MrBatschner
MrBatschner previously approved these changes Jan 30, 2025
Copy link
Contributor

@MrBatschner MrBatschner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@gardener-robot gardener-robot added reviewed/lgtm Has approval for merging and removed needs/review Needs review labels Jan 30, 2025
@gardener-robot-ci-1 gardener-robot-ci-1 added reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Jan 30, 2025
@gardener-robot gardener-robot added needs/review Needs review kind/api-change API change with impact on API users needs/second-opinion Needs second review by someone else size/l Size of pull request is large (see gardener-robot robot/bots/size.py) and removed needs/review Needs review labels Jan 30, 2025
@gardener-robot-ci-1 gardener-robot-ci-1 added the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Jan 30, 2025
@gardener-robot gardener-robot removed reviewed/lgtm Has approval for merging size/m Size of pull request is medium (see gardener-robot robot/bots/size.py) labels Jan 30, 2025
@gardener-robot-ci-3 gardener-robot-ci-3 removed the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Jan 30, 2025
test/integration/container-runtime/container_runtime.go Outdated Show resolved Hide resolved
g.Expect(string(response)).To(g.Equal(fmt.Sprintf("%s\n", "1")))
g.Expect(string(errorResponse)).To(g.Equal(fmt.Sprintf("%s\n", "1")))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really the right variable that holds the exit code?

Copy link
Contributor

@MrBatschner MrBatschner Feb 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, you are right, this test was bad. We are running a Pod that greps and counts how many times "gVisor" was found in dmesgs output. If grep would return something on stderr, it would probably return with an err anyway and we check for that. Hence, removing any glance at stderr and restoring this tests to what it was before.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, now we check twice for: g.Expect(err).ToNot(g.HaveOccurred())
Otherwise looks good.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, now we check twice for: g.Expect(err).ToNot(g.HaveOccurred()) Otherwise looks good.

Argh... 🤦 Fixed, PTAL.

@gardener-robot gardener-robot added the needs/changes Needs (more) changes label Jan 31, 2025
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 6, 2025

A newer version of github.com/gardener/gardener exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

@gardener-robot-ci-3 gardener-robot-ci-3 added reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Feb 6, 2025
@MrBatschner
Copy link
Contributor

@Roncossek Fixed your suggestions, PTAL

@MrBatschner MrBatschner requested a review from Roncossek February 6, 2025 09:16
@gardener-robot-ci-2 gardener-robot-ci-2 added reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Feb 6, 2025
@Roncossek Roncossek merged commit 1b827b4 into master Feb 6, 2025
12 checks passed
@Roncossek Roncossek deleted the dependabot/go_modules/github.com/gardener/gardener-1.111.1 branch February 6, 2025 12:03
@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code kind/api-change API change with impact on API users needs/changes Needs (more) changes needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/second-opinion Needs second review by someone else size/l Size of pull request is large (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.

6 participants