We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Never Kubernetes releases enable RBAC by default, which means that this pod won't be able to requests API unless policy is created.
It would be nice to have an example of role and rolebinding.
The text was updated successfully, but these errors were encountered:
Example policy that works on our cluster:
kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: namespace: monitoring name: slack-events-watcher rules: - apiGroups: [""] # "" indicates the core API group resources: ["events"] verbs: ["list", "watch", "get"] --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: namespace: monitoring name: watch-events subjects: - kind: ServiceAccount name: default namespace: monitoring apiGroup: "" roleRef: kind: ClusterRole name: slack-events-watcher apiGroup: rbac.authorization.k8s.io
Sorry, something went wrong.
No branches or pull requests
Never Kubernetes releases enable RBAC by default, which means that this pod won't be able to requests API unless policy is created.
It would be nice to have an example of role and rolebinding.
The text was updated successfully, but these errors were encountered: