Closed rhenretta closed 7 years ago
I thought it might be related to the Targets being unknown. Fixed it, but still see the same behavior
The overall situation for HPAs is that they are still alpha, and we added UI support for them a little too early. Still working out a plan, but we might end up removing it from the UI until they reach beta.
My understanding is that custom metrics are still in alpha, not all of HPA. Lots of K8s apis are in that kind of state I'm guessing. I don't think adding a view only list of which HPA are created in the web console is too soon, it's like doing a kubectl get hpa which works just fine, but isn't as pretty or convenient as the Tectonic Console. Just my 2cents.
The Horizontal Pod Autoscaler is an API resource in the Kubernetes autoscaling API group. The current stable version, which only includes support for CPU autoscaling, can be found in the autoscaling/v1 API version. The alpha version, which includes support for scaling on memory and custom metrics, can be found in autoscaling/v2alpha1. The new fields introduced in autoscaling/v2alpha1 are preserved as annotations when working with autoscaling/v1.
"/apis/autoscaling",
"/apis/autoscaling/v1",
"/apis/autoscaling/v2alpha1",
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
This has since been removed from the Console because it was an alpha feature that introduced breaking API changes. We may add it back at some point in the future once the upstream Kubernetes API stabilizes.
Is this a BUG REPORT or FEATURE REQUEST?
Bug report
Versions
What happened?
I created an autoscaler for a deployment in kubectl. When I go to view the autoscalers, it hangs, and the console has the following output:
I can see the deplpoyments with kubectl: