Corrected the verion of gateway api controller #662
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
documentation
Which issue does this PR fix:
You encounter an error in AWS Gateway API Controller after deploying the gateway. The logs indicate that there are missing permissions for tlsroutes in ClusterRole.
Logs from AWS Gateway API Controller pod:
Error: E0904 23:06:10.238076 1 reflector.go:147] pkg/mod/k8s.io/client-go**@v0.28.3/tools/cache/reflector.go:229:** Failed to watch *v1alpha2.TLSRoute: failed to list *v1alpha2.TLSRoute: tlsroutes.gateway.networking.k8s.io is forbidden: User "system:serviceaccount:aws-application-networking-system:gateway-api-controller" cannot list resource "tlsroutes" in API group "gateway.networking.k8s.io" at the cluster scope
What does this PR do / Why do we need it:
There is a difference in version of AWS Gateway API Controller in the blog. The controller installation mentions the version as V1.0.6 but as we proceed with the blog it talks about the updating the AWS Gateway API Controller for updating defaultServiceNetwork. This command has a different version
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
Testing done on this change:
Yes
Automation added to e2e:
NA
Will this PR introduce any new dependencies?:
NA
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No
Does this PR introduce any user-facing change?:
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.