-
Notifications
You must be signed in to change notification settings - Fork 890
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
eliminate insecureSkipTLSVerify=true in karmada #4024
Comments
/assign |
I guess you mean this piece of code: Why can not be removed? |
@RainbowMango yes, is this line: karmada/pkg/karmadactl/register/register.go Lines 835 to 848 in f2c7d0b
The corresponding code are building 1、member cluster use 2、member cluster use 3、 write if remove |
Thanks for the clarification. |
@RainbowMango: Closing this issue. 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/test-infra repository. |
What would you like to be added:
insecureSkipTLSVerify=true
means prohibit clientside from verifing the cert of serverside, this is an unsafe configuration, we can avoid unnecessary unsafe configurations.insecureSkipTLSVerify
in YAML artifacts used bydeploy-karmada.sh
. (verification method: exechack/local-up-karmada.sh
success) remove insecureSkipTLSVerify in local-up-karmada script #4026insecureSkipTLSVerify
inkarmadactl init
. (verification method: execkarmadactl init
success). remove insecureSkipTLSVerify in karmadactl #4061insecureSkipTLSVerify
in helm chart. (verification method: exechelm install
success). remove insecureSkipTLSVerify in helm chart #4033insecureSkipTLSVerify
in test code. remove insecureSkipTLSVerify in UT test #4062insecureSkipTLSVerify
in operator (verification method: install by operator success). remove insecureSkipTLSVerify in operator #40636. removeinsecureSkipTLSVerify
inkarmadactl register
. (just one line, can not be deleted)Why is this needed:
avoid unnecessary unsafe configurations.
The text was updated successfully, but these errors were encountered: