You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That comment provides easy steps a user can do in order to quickly test their remote cluster secret's kubeconfig. We can tweek those instructions for the FAQ as necessary. But in short, we need to check that the kubeconfig is authorized to "watch" resources and it should be able to "get" resources as well. We should consult the server Role and see if we can get the FAQ to be able to check for as many as we can.
The text was updated successfully, but these errors were encountered:
We should add an FAQ entry on how to test a remote cluster secret to help debug issues with the kubeconfig.
See: #8356 (comment)
That comment provides easy steps a user can do in order to quickly test their remote cluster secret's kubeconfig. We can tweek those instructions for the FAQ as necessary. But in short, we need to check that the kubeconfig is authorized to "watch" resources and it should be able to "get" resources as well. We should consult the server Role and see if we can get the FAQ to be able to check for as many as we can.
The text was updated successfully, but these errors were encountered: