-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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: handle incorrect cluster RESTconfig without panic #20150
base: master
Are you sure you want to change the base?
fix: handle incorrect cluster RESTconfig without panic #20150
Conversation
✅ Preview Environment deployed on Bunnyshell
See: Environment Details | Pipeline Logs Available commands (reply to this comment):
|
✅ Preview Environment created on Bunnyshell but will not be auto-deployedSee: Environment Details Available commands (reply to this comment):
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #20150 +/- ##
==========================================
- Coverage 55.89% 55.87% -0.03%
==========================================
Files 321 321
Lines 44497 44540 +43
==========================================
+ Hits 24871 24886 +15
- Misses 17053 17076 +23
- Partials 2573 2578 +5 ☔ View full report in Codecov by Sentry. |
04ac06e
to
87a08dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
Could you add tests for the behavior of adding a cluster with both insecure and CA data?
87a08dc
to
db78f3f
Compare
Signed-off-by: cef <[email protected]>
db78f3f
to
4091db1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
fixes #19496
The issue arises when a cluster has its secret configuration set with
insecure
astrue
but includes a non-emptycaData
. This PR resolves the issue by handling the error gracefully rather than causing a panic.Testing Instruction
kind create cluster
.yq
is needed to run the command):In my case, the following is generated
/tmp/kind-cluster-secret.yaml
:Create the secret by running
kubectl apply -f /tmp/kind-cluster-secret.yaml
.insecure
totrue
then update the secret:Trace
Checklist: