-
Notifications
You must be signed in to change notification settings - Fork 213
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
custom-metrics-stackdriver-adapter not working - auth problems? #498
Comments
Looks like I have the same issue:
|
I have the same issue |
I have a high volume of the same / similar errors |
Same issue, also I had to add this resource to my cluster in order to get it to startup apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: custom-metrics-extension-apiserver-authentication-reader
namespace: kube-system
subjects:
- kind: ServiceAccount
name: custom-metrics-stackdriver-adapter
namespace: custom-metrics
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: extension-apiserver-authentication-reader |
I tried this but nothing changed. When you "get it to startup" what exactly does "it" refer to? The stackdriver adapter pod? In my case the pod is running, but it
Maybe it's a different issue? |
@PaulRudin just spitballing here, but that error looks like your cluster's service account doesn't have permission to call the GCP monitoring API. |
Yeah, but nothing has changed recently as far as I know. But maybe I've inadvertently modified something when changing something unrelated. |
Hi! I have the exactly same issue and it appeared suddenly about the same period. I thought too about a permission or scope issue but the node where the adapter is running has I also think that it is not a permission or scope issue as we have timeout errors. I am still investigating. Maybe something has changed on GCP side. |
OK - so in my case I had inadvertently changed the service account, so the permission denied problem has been fixed. But I do still see messages similar to those reported by others:
|
sorry to slightly hijack, but also curious what folks who are using Workload Identity do - do you create a GCP service account for the custom metrics adapter and bind it to the Kube service account? I assume the cluster role bindings don't provide Google API level access, and with workkload identity, I don't think the pod will implicitly have the creds of the nodepool's service account either. #315 I guess kind of covers this |
We're seeing the same error messages but the adapter appears to be functional. It would be nice to understand what the errors mean and what changes we need to make to reduce the noise. |
@sosimon how do you test to know it is functional? are you reading a metric with kubectl ? |
Hi have created a new GCP project and a GKE cluster inside it.
I've followed the instructions in the README...
However Logs Explorer is complaining about it... looks like an authentication problem?
The text was updated successfully, but these errors were encountered: