Open jim-docker opened 1 year ago
The issue with resource creation (clusterroles
, clusterrolebindings
) can be resolved by running:
kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=<user-name>
where <user-name>
is the user associated with the kube context you are using (look at the kubecong, kubectl config view
)
If creating the clusterrolebinding
fails, i.e.
User "<user-name>" cannot create clusterrolebindings.rbac.authorization.k8s.io at the cluster scope.:
"Required \"container.clusterRoleBindings.create\" permission."
(post clusterrolebindings.rbac.authorization.k8s.io)
then you first need more permissions at the GCP level, in the associated project, for you as user person@company.com
. You, or someone with higher permissions, must run
gcloud projects add-iam-policy-binding $PROJECT \
--member=user:person@company.com \
--role=roles/container.admin
Then retry creating the clusterrolebinding
The remaining issue is related to node-exporter trying to access /
and /proc
and /sys
which is not allowed by autopilot. The ultimate solution may be to instead support one of the GCP managed services for metrics (See https://stackoverflow.com/a/73066153)
did anyone make it work? It installs but it still doesn't show any Metrics
few other problems maybe too