-
Notifications
You must be signed in to change notification settings - Fork 479
[Fix] Remove remote client of insecurely setup cluster #7486
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
[Fix] Remove remote client of insecurely setup cluster #7486
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
|
LGTM, I will merge after rebased |
2f4a1fe to
295e18d
Compare
b8fd915 to
3192ea5
Compare
3192ea5 to
a65a2f7
Compare
|
/lgtm |
|
@mimowo: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
LGTM label has been added. Git tree hash: e375806e3444d60a3cb21983ba96d08686918dc0
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo, mszadkow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-kueue-test-integration-baseline-main |
|
@mimowo: #7486 failed to apply on top of branch "release-0.14": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mimowo: #7486 failed to apply on top of branch "release-0.13": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Even though we validate and prevent the use of invalid/insecure kubeconfigs, the remoteClient of the Cluster that kuebconfig was updated with invalid kubeconfig still remains on the list of valid clusters.
Because of that it is still possible to admit a workload to this cluster.
To give a stronger message to the user that Kubeconfig was improperly updated remoteClient will be removed from the clusterReconciler remoteClients list.
Which issue(s) this PR fixes:
Relates to this PR: #7483
Special notes for your reviewer:
Does this PR introduce a user-facing change?