It causes many problems on deployment, I spent about an hour debugging why the controller can't list PVC/Storage classes.
ClusterRoleBinding should be created in the same namespace. If we specify one in yaml and decide to use -n namespace in kubectl command, it will not create them in the same ns.
It causes many problems on deployment, I spent about an hour debugging why the controller can't list PVC/Storage classes. ClusterRoleBinding should be created in the same namespace. If we specify one in yaml and decide to use
-n namespace
in kubectl command, it will not create them in the same ns.