This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hey, Using EKS and metrics-server(from the helm chart) I have this error, I created the cluster using the pulumi guide with EKS and node groups. I have the aws-node, with the CNI installed (but not the addon)

E0729 17:05:11.585565       1 scraper.go:149] "Failed to scrape node" err="Get \"<https://10.0.12.191:10250/metrics/resource>\": remote error: tls: internal error" node="ip-10-0-12-191.us-west-2.compute.internal"
E0729 17:05:46.982621       1 scraper.go:147] "Failed to scrape node, timeout to access kubelet" err="Get \"<https://10.0.158.73:10250/metrics/resource>\": context deadline exceeded" node="ip-10-0-158-73.us-west-2.compute.internal" timeout="10s"

I have other deployment working fine, Also I can use HPA with CPU based autoscaling. But I have random warning in the cluster by the HPA (failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)\

This message was deleted.

This message was deleted.

This message was deleted.

Hi! I’m getting started creating a dynamic resource provider in python and I have a couple of questions. • It seems that it isn't possible to access config secrets/values from within the dynamic resource provider. Is that correct? • For the id of the resource being made, is it better to use the name of the resource, something like a UUID created by the cloud provider, or is there some other best practice? Thank you!

This message was deleted.