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.

Sign up for GitHub

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

Jump to bottom

Add documentation for known GKE issue detailed in issue 515 #237

Merged
merged 1 commit into from
Aug 25, 2020
Merged

Add documentation for known GKE issue detailed in issue 515 #237

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions content/troubleshooting/gke-external-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
+++
title = "Why does Google Kubernetes Engine (GKE) 1.16 fail to fetch external metrics?"
+++

If you are running Google Kubernetes Engine (GKE) version 1.16, and are receiving the following error:

```
unable to fetch metrics from external metrics API: <METRIC>.external.metrics.k8s.io is forbidden: User "system:vpa-recommender" cannot list resource "<METRIC>" in API group "external.metrics.k8s.io" in the namespace "<NAMESPACE>": RBAC: clusterrole.rbac.authorization.k8s.io "external-metrics-reader" not found
```

You are almost certainly running into a [known issue](https://issuetracker.google.com/issues/160597676).

The workaround is to recreate the `external-metrics-reader` role using the following YAML:

```
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: external-metrics-reader
rules:
- apiGroups:
- "external.metrics.k8s.io"
resources:
- "*"
verbs:
- list
- get
- watch
```

The GKE team is currently working on a fix that they expect to have out in version >= 1.16.13.