Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Clean-up
Which issue does this PR fix:
N/A - Proactive dependency maintenance
What does this PR do / Why do we need it:
This PR upgrades key Kubernetes dependencies to their latest versions and fixes API compatibility issues introduced by the upgrades. The changes include:
Dependency Upgrades:
sigs.k8s.io/controller-runtime: v0.20.2 → v0.22.1k8s.io/api: v0.32.2 → v0.34.1k8s.io/client-go: v0.32.2 → v0.34.1github.com/stretchr/testify: v1.10.0 → v1.11.1golangci-lint: v1.63.4 → v2.4.0API Compatibility Fixes:
apiutil.RESTClientForGVKfunction signature change (added missing boolean parameter)res.RequeuewithRequeueAfterpattern in controllerscorev1.Endpointstodiscoveryv1.EndpointSliceAPIRequeueAfterinstead of deprecatedRequeuefieldThese upgrades provide the latest bug fixes, security patches, and performance improvements from the Kubernetes ecosystem.
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
N/A - This is a proactive maintenance upgrade
Testing done on this change:
go build ./...go vet ./...Automation added to e2e:
No new e2e tests required - existing tests cover the same functionality with updated APIs
Will this PR introduce any new dependencies?:
No new external dependencies. Only upgraded existing Kubernetes client libraries to newer versions.
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No breaking changes for running clusters. The changes are internal API usage updates that maintain backward compatibility for deployed resources. The controller behavior remains functionally identical.
Does this PR introduce any user-facing change?:
No user-facing changes. All modifications are internal dependency upgrades and API compatibility fixes.