Bump github.com/gardener/gardener from 1.75.1 to 1.76.0

[dependabot]

Bumps github.com/gardener/gardener from 1.75.1 to 1.76.0.

Release notes

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

v1.76.0

[gardener/gardener]

⚠️ Breaking Changes

• [OPERATOR] Removed service.beta.kubernetes.io/aws-load-balancer-type: nlb annotation from istio-ingressgateway service template. Set this annotation in seed configuration. Note: Changing load balancer type creates a new one, old one requires manual clean-up. by @​axel7born #8214
• [OPERATOR] When deploying this version of gardener-operator, make sure that you update your Garden resources with the new .spec.virtualCluster.gardener.clusterIdentity field. If you already have a gardener-apiserver deployment, make sure that the value matches the --cluster-identity flag of the current gardener-apiserver deployment. by @​rfranzke #8234
• [OPERATOR] gardener-operator no longer reports the Reconciled condition. Instead, it now reports the progress in .status.lastOperation, similar to how it's done for Shoots. by @​rfranzke #8238
• [OPERATOR] ⚠️ The deprecated field .spec.settings.ownerChecks has been removed from the Seed API. Please check your Seeds and remove any usage before upgrading to this Gardener version. by @​dimitar-kostadinov #8109
• [DEVELOPER] So far the github.com/gardener/gardener/pkg/utils/managedresources.{NewForShoot,CreateForShoot} funcs were ignoring the passed origin func parameter and were always using gardener as value. These funcs will now respect and use the passed origin value. by @​ialidzhikov #8260
• [DEVELOPER] A new field errorCodeCheckFunc is introduced in the generic Worker actuator. This should be set to parse the Gardener error codes from the error returned in Worker reconciliation. by @​acumino #8242

✨ New Features

• [OPERATOR] Add Care reconciler to Garden controller in gardener-operator. by @​oliver-goetz #8158
• [OPERATOR] Shoots allow to optionally configure a specific scheduler via .spec.schedulerName. The default-scheduler is used in case non is configured. Please note, that Shoots will remain Pending in case a scheduler name is configured but an adequate scheduler is not available in the landscape. by @​timuthy #8261

🐛 Bug Fixes

• [USER] An issue has been fixed which caused CoreDNS to not rewrite CNAME values in DNS answers. by @​axel7born #8231
• [DEVELOPER] A bug in the local development environment has been fixed which prevented admission of Gardener resources by extension webhooks. by @​vpnachev #8239
• [OPERATOR] The obsolete addons ManagedResource is now properly cleaned up. by @​shafeeqes #8233
• [OPERATOR] Now the vali ingress definition points to the shoot logging service. by @​nickytd #8252

🏃 Others

• [OPERATOR] Stability of the ssh tunnel in the local extension setup should improve due to better failure handling. by @​ScheererJ #8236
• [OPERATOR] Following dependency has been updated:-
  • github.com/gardener/etcd-druid v0.18.1 -> v0.18.4 by @​acumino #8228
• [USER] It is now possible to enable disabled APIs for workerless shoot clusters via spec.kubernetes.kubeAPIServer.runtimeConfig. by @​timuthy #8258

[gardener/dependency-watchdog]

🏃 Others

• [DEVELOPER] update client-go version and exclude the old one in go.mod by @​acuminogardener/dependency-watchdog#90

Commits

• a5a76db Release v1.76.0
• ca999b8 Drop no longer needed checksum annotations from GCM deployment (#8270)
• e18c332 [operator] Introduce gardenerscheduler Golang component (#8262)
• e286e4e [operator] Add Gardener Scheduler options to Garden API (#8265)
• afa8ef9 [operator] Introduce gardeneradmissioncontroller Golang component (#8244)
• 6f8ce76 Move seed-monitoring and shoot-core charts and monitoring-related logic i...
• 0426cfe Introduce .spec.schedulerName in Shoot API (#8261)
• 63346c3 Enhance error code detection in worker controller (#8242)
• fa50315 Release responsible schedule for v1.79 until v1.87 (#8226)
• ac26953 [operator] Add component instantiation/deploy functions for `gardenerapiserve...
• Additional commits viewable in compare view

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 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)