Closed gyliu513 closed 7 years ago
You don't need cluster admin for pilot itself, just for the user running the istio install
Can you start from a fresh cluster or delete all crd in your cluster before you install ? (and make sure you install the -rbac-beta file before the rest)
I want to give istio-pilot-service-account
all of the permissions to make sure it can works.
Another question is that, from the log here I did not see any reasons, but only telling me * failed to register custom resources. <nil>
, I do not know what to do for such cases, but only blindly update clusterrolebindings based on my experience. I think that we may need to check more for what is wrong with the problem, why the error is nil
here? @ldemailly
I want to give istio-pilot-service-account all of the permissions to make sure it can works.
as I said the istio-rbac-beta.yaml covers everything pilot needs. and if it doesn't we would need to know to fix it, not apply cluster admin
can you start from a fresh cluster, indicate which kubernetes version you are using and the exact steps you took and see if you can reproduce this
This is likely due to removal of dashes from CRD names (a one-time thing). Let me know if it still happens after you clean up all CRDs.
I have the same problem , I Solve problems by deleting all old crd of the config.istio.io
I was deploying istio from source code of https://github.com/istio/istio/blob/master/install/kubernetes/istio.yaml
After pilot is deployed, it keeps failing due to following:
After I assign
cluster-admin
role todefault:istio-pilot-service-account
, still failed.Can someone help check what is wrong? Thanks.