Skip to content
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

When running on k8s 1.18.6, clusterpedia failed to run #381

Closed
panpan0000 opened this issue Sep 21, 2022 · 3 comments
Closed

When running on k8s 1.18.6, clusterpedia failed to run #381

panpan0000 opened this issue Sep 21, 2022 · 3 comments
Labels
question Further information is requested

Comments

@panpan0000
Copy link
Contributor

What happened?

error message:
企业微信截图_4378897b-7dc5-40e5-8033-78942644161b

What did you expect to happen?

it run well

How can we reproduce it (as minimally and precisely as possible)?

1.18

Anything else we need to know?

No response

Clusterpedia Version

# replace the pod name of clusterpedia apiserver
$ kubectl -n clusterpedia-system exec {clusterpedia-apiserver-pod-name} -- apiserver --version=raw
# paste output here

# replace the pod name of clusterpedia clustersynchro-manager
$ kubectl -n clusterpedia-system exec {clustersynchro-manager-pod-name} -- clustersynchro-manager --version=raw
# paste output here

Host Kubernetes version

$ kubectl version
# paste output here
@panpan0000 panpan0000 added the kind/bug Something isn't working label Sep 21, 2022
@clusterpedia-bot
Copy link

Hi @panpan0000,
Thanks for opening an issue!
We will look into it as soon as possible.

Details

Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.

@Iceber
Copy link
Member

Iceber commented Sep 22, 2022

This is because the front-proxy-client.crt used by your kube-apiserver is using SHA1, it is recommended to recreate front-proxy-client.crt, SHA1 has security issues.

spec:
  containers:
  - command:
    - kube-apiserver
    - --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt
    - --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key

golang has rejected SHA1 since 1.18 golang/go#41682, of course it is possible to use the environment variable GODEBUG=x509sha1=1 to allow sha1 certificates, but this is still insecure.

However, to be compatible with more user scenarios, we will add a value to helm to help users configure the environment variable GODEBUG=x509sha1=1.

@Iceber Iceber added the question Further information is requested label Sep 22, 2022
@Iceber Iceber removed the kind/bug Something isn't working label Sep 22, 2022
@Iceber Iceber closed this as completed Sep 23, 2022
@panpan0000
Copy link
Contributor Author

Thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants