search

kubernetes-sigs / descheduler

Descheduler for Kubernetes
https://sigs.k8s.io/descheduler
Apache License 2.0
4.24k stars 645 forks source link

cannot verify signature: insecure algorithm SHA1-RSA #1265

Closed chuqiao8250 closed 3 months ago

chuqiao8250 commented 8 months ago

What version of descheduler are you usinI1017 08:43:12.561417 1 named_certificates.go:53] "Loaded SNI cert" index=0 certName="self-signed loopback" certDetail="\"apiserver-loopback-client@1697532192\" [serving] validServingFor=[apiserver-loopback-client] issuer=\"apiserver-loopback-client-ca@1697532192\" (2023-10-17 07:43:11 +0000 UTC to 2024-10-16 07:43:11 +0000 UTC (now=2023-10-17 08:43:12.561352834 +0000 UTC))" I1017 08:43:12.561520 1 secure_serving.go:210] Serving securely on [::]:10258 I1017 08:43:12.561625 1 tlsconfig.go:240] "Starting DynamicServingCertificateController" I1017 08:43:12.581222 1 descheduler.go:111] "Warning: Get Kubernetes server version fail" E1017 08:43:12.599495 1 server.go:99] "descheduler server" err="Get \"https://10.254.0.1:443/api\": tls: failed to verify certificate: x509: certificate signed by unknown authority (possibly because of \"x509: cannot verify signature: insecure algorithm SHA1-RSA (temporarily override with GODEBUG=x509sha1=1)\" while trying to verify candidate authority certificate \"192.168.26.33\")" I1017 08:43:12.599720 1 tlsconfig.go:255] "Shutting down DynamicServingCertificateController" I1017 08:43:12.599728 1 secure_serving.go:255] Stopped listening on [::]:10258g?

descheduler version:

Does this issue reproduce with the latest release?

Which descheduler CLI options are you using?

Please provide a copy of your descheduler policy config file

What k8s version are you using (kubectl version)?

kubectl version Output
$ kubectl version

What did you do?

What did you expect to see?

What did you see instead?

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 3 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1265#issuecomment-2028096735): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.