fixing upjet aws provider v1.3.0 bug with ClusterAuth #189
Conversation
This file contains 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
edgarsilva948
requested review from
nabuskey,
vara-bonthu,
nimakaviani,
candonov,
csantanapr,
7navyasa and
johnphilips3
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 does this PR do?
This pull request updates the provider-upjet-aws version to v1.4.0 in Crossplane configuration. This version update addresses a critical issue where the ClusterAuth resource was incorrectly handling kubeconfig authorizations, leading to unauthorized errors when interacting with EKS clusters.
Motivation
I found this issue with the ClusterAuth resource while using the provider-upjet-aws v1.3.0, where it resulted in unauthorized errors when trying to generate kubeconfig for EKS clusters.
More
Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
Yes, I have added a new example under examples to support my PR
Yes, I have updated the docs for this feature
Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)
Note:
For Moderators
Additional Notes