-
Notifications
You must be signed in to change notification settings - Fork 557
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
kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1 won't work #66
Comments
@DirectXMan12 any ideas? |
You probably just need to make your own image. try to curl /apis to see what options you have. |
Same issue for me. Got over it by getting the image 'directxman12/k8s-prometheus-adapter:advanced-config' instead of 'directxman12/k8s-prometheus-adapter:v0.1.0-centos' |
Actually I spoke too soon, the upgrade to the latest image will work for Kubernetes 1.8+. I'm attempting to run HPA with custom-metrics on kubernetes 1.7. While switching to the advanced-config image did help with 'kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1', but the HPA was still throwing the following errors:
Looking at these it indicates that the HPA is expecting the custom metrics to be available at the path "custom-metrics.metrics.k8s.io", and not "custom.metrics.k8s.io". So, I changed the API Service definition to refer to the group custom-metrics.metrics.k8s.io. Deployed the apiserver again, but now the 'kubectl raw' command failed. The custom-metrics-apiserver logs logged a 404 for the path "/apis/custom-metrics.metrics.k8s.io/v1beta1". So, it was getting the request but didnt know how to serve it. I dug a bit into the https://github.com/kubernetes/metrics/ and found this commit: Taking that and from kubernetes/metrics figured out that the group version needs to be 'v1apha1'. So, I switched back to directxman12/k8s-prometheus-adapter:v0.1.0-centos and updated the API Service yaml as follows for Kubernetes 1.7:
Post re-deploying the apiserver, etc I was able to successfully execute "kubectl get --raw "/apis/custom-metrics.metrics.k8s.io/v1alpha1", and even the HPA was able to get to my custom Pod metrics. Hope this helps someone. |
Only v0.1.0 works on Kubernetes 1.7, as noted in the release notes of v0.2.0. |
…ncy-openshift-4.13-ose-prometheus-adapter Updating ose-prometheus-adapter images to be consistent with ART
I've been trying to get this going and I'm just missing something, I think there is a good chance its related to RBAC. I've tried to follow Walk Through , Deploy and Helm Chart but can't get any of them to work.
I was able to get Luxas Walkthrough to work end to end. To eliminate additional complexities I tried to use madeden Helm chart with self-signed certs. And also edit above to use self-signed in case there were issues there. I've gone over RBAC and tried to add some more open privileges for testing, but have only limitedly dealt with RBAC.
I don't see any errors til the pod service starts:
When I turn on more verbose logging I'm seeing a lot of things like:
I've been trying to look at the difference b/t the 2, but I feel like I'm spinning my wheels a little, hoping with the details and fact that I can get Luxas to work will help surface my issue. More than happy to post anything that will help.
The text was updated successfully, but these errors were encountered: