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

couldn't get resource list for custom.metrics.k8s.io/v1beta1 #5922

Closed
tekumara opened this issue Aug 16, 2022 · 2 comments
Closed

couldn't get resource list for custom.metrics.k8s.io/v1beta1 #5922

tekumara opened this issue Aug 16, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@tekumara
Copy link

Expected Behavior

Current Behavior

          api │ STEP 3/3 — Deploying
          api │      Applying YAML to cluster
E0816 22:07:19.560706   77642 memcache.go:196] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
E0816 22:07:19.560706   77642 memcache.go:196] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
E0816 22:07:19.560706   77642 memcache.go:196] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
          api │      Objects applied to cluster:
          api │        → api:service
          api │        → api:deployment

Steps to Reproduce

  1. Run tilt up in the https://github.com/tilt-dev/tilt-avatars against an EKS cluster

Context

tilt doctor Output

$ tilt doctor
Tilt: v0.30.7, built 2022-08-12
System: darwin-arm64
---
Docker
- Host: unix:///var/run/docker.sock
- Server Version: 20.10.17
- API Version: 1.41
- Builder: 2
- Compose Version: v2.6.1
---
Kubernetes
- Env: unknown
- Context: myorg
- Cluster Name: myorg.com
- Namespace: prefect-tools
- Container Runtime: read-failure
- Version: v1.20.15-eks-84b4fe6
- Cluster Local Registry: none
---

About Your Use Case

@tekumara tekumara added the bug Something isn't working label Aug 16, 2022
@nicks
Copy link
Member

nicks commented Aug 16, 2022

AFAICT, this error means you have a misconfigured cluster:
kyverno/kyverno#1481
aws/amazon-vpc-cni-k8s#486 (comment)

and so the underlying kubernetes libraries we're using are trying to warn you about it. The external metric API is enabled, but no handler is declared.

@tekumara
Copy link
Author

Great thankyou! I'll close this and follow up with my cluster admins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants