Skip to content
This repository has been archived by the owner on May 20, 2020. It is now read-only.

Fail to create CRD on start #46

Open
fiftoine opened this issue Jun 11, 2018 · 1 comment
Open

Fail to create CRD on start #46

fiftoine opened this issue Jun 11, 2018 · 1 comment

Comments

@fiftoine
Copy link

fiftoine commented Jun 11, 2018

Hi,

As is, the operator can't create CRDs if not given some permissions.

Applying this makes it work (assuming you deploy on the default namespace) :

Maybe some extra documentation on the README.md file to tell permissions are needed would be nice ;-)

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: operator-kafka
rules:
- apiGroups:
  - krallistic.github.com
  resources:
  - "*"
  verbs:
  - "*"
- apiGroups:
  - ""
  resources:
  - pods
  - services
  - endpoints
  - persistentvolumeclaims
  - events
  - configmaps
  - secrets
  verbs:
  - "*"
- apiGroups:
  - apps
  resources:
  - deployments
  - daemonsets
  - replicasets
  - statefulsets
  verbs:
  - "*"
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - '*'

---

kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: default-account-operator-kafka
subjects:
- kind: ServiceAccount
  name: default
  namespace: default
roleRef:
  kind: ClusterRole
  name: operator-kafka
  apiGroup: rbac.authorization.k8s.io

@Mrart
Copy link

Mrart commented Jan 14, 2020

Can you push it to this project!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants