-
Notifications
You must be signed in to change notification settings - Fork 422
wait-for-endpoints init-containers fails to load with k8s 1.6.0 #56
Comments
For reference, I was able to resolve the new 1.6 RBAC reqirements by giving it "god" mode
This is not a long term solution but it will work as a hack for now. Could you please provide a better "read-only" RBAC for 1.6? |
FYI I also believe this issue is related to #48 |
strange - I am getting:
|
that command is new in kubectl 1.6.0 |
Boom - that was it. |
we're also running into this. been debugging for 2 hours now. to me it seems it's just an issue with because this works curl -s --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt --header \"Authorization: Bearer \"(cat /var/run/secrets/kubernetes.io/serviceaccount/token) https://kubernetes.default.svc/api/v1/namespaces/monitoring/endpoints/grafana but when i do: set endpoints (curl -s --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt --header \"Authorization: Bearer \"(cat /var/run/secrets/kubernetes.io/serviceaccount/token) https://kubernetes.default.svc/api/v1/namespaces/monitoring/endpoints/grafana); echo $endpoints; then never used fish before, any ideas? |
@chapati23 Try this command:
Change it in
There is no need to set |
I wouldn't recommend getting in the habit of using |
Hi,
I just updated to k8s 1.6.0 (via kubeadm) and found that the
grafana-import-dashboards
job is failing to pick up the kubernetes api.I am assuming this is because of the new RBAC roles that were added to 1.6 but I am unsure of how to fix this issue or hack around it.
I believe this issue is around this block of code.
Here is some debugging information.
Pods
logs for the initContainer
I am able to hit the endpoint api via dashboard
The text was updated successfully, but these errors were encountered: