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.

Sign up for GitHub

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

Jump to bottom

Not able to kubectl -n alteragoto get pods #13041

Closed
anishrajpoudel opened this issue Jan 10, 2025 · 1 comment
Closed

Not able to kubectl -n alteragoto get pods #13041

anishrajpoudel opened this issue Jan 10, 2025 · 1 comment
Labels
kind/question QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@anishrajpoudel
Copy link

E0109 17:11:10.338738 3049 memcache.go:265] couldn't get current server API group list: Get "https://amr-caas.sc.altera.com/k8s/clusters/c-m-kbzr8m5r/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0109 17:11:10.368622 3049 memcache.go:265] couldn't get current server API group list: Get "https://amr-caas.sc.altera.com/k8s/clusters/c-m-kbzr8m5r/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0109 17:11:10.394316 3049 memcache.go:265] couldn't get current server API group list: Get "https://amr-caas.sc.altera.com/k8s/clusters/c-m-kbzr8m5r/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0109 17:11:10.420376 3049 memcache.go:265] couldn't get current server API group list: Get "https://amr-caas.sc.altera.com/k8s/clusters/c-m-kbzr8m5r/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
E0109 17:11:10.445235 3049 memcache.go:265] couldn't get current server API group list: Get "https://amr-caas.sc.altera.com/k8s/clusters/c-m-kbzr8m5r/api?timeout=32s": tls: failed to verify certificate: x509: certificate signed by unknown authority
Unable to connect to the server: tls: failed to verify certificate: x509: certificate signed by unknown authority
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 10, 2025
@richard-cox
Copy link
Member

This doesn't look like a Rancher UI issue.

If this is a hosted rancher please consider contacting the provider, or if it is a general rancher issue please raise a new gh issue over at rancher/rancher

@richard-cox richard-cox closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richard-cox @anishrajpoudel