-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
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
cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers #98
Comments
Hi @zetaab, I've never seen such those errors on any of our logs. Have you set any finalizer specifically? I think that you may fix this allowing (in the RBAC) the service account to access to the finalizers api. I don't know if you have a special configuration or if OpenShift has it by default. Unfortunately, we cannot support OpenShift. Maybe some other user has faced this error before and knows how to fix it. |
Add apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: redisoperator
rules:
- apiGroups:
- storage.spotahome.com
resources:
- redisfailovers
- redisfailovers/finalizers
verbs:
- "*"
- apiGroups:
- apiextensions.k8s.io
resources:
- customresourcedefinitions
verbs:
- "*"
- apiGroups:
- ""
resources:
- pods
- services
- endpoints
- events
- configmaps
verbs:
- "*"
- apiGroups:
- apps
resources:
- deployments
- statefulsets
verbs:
- "*"
- apiGroups:
- policy
resources:
- poddisruptionbudgets
verbs:
- "*" |
Needed for setting KubeletConfig as the OwnerReference: spotahome/redis-operator#98 Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Needed for setting KubeletConfig as the OwnerReference: spotahome/redis-operator#98 Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Expected behaviour
I want to install new redis HA setup in openshift
Actual behaviour
I can create redis-operator just fine. However, when I create new redisfailover with https://github.com/spotahome/redis-operator/blob/master/example/redisfailover/persistant-storage.yaml
the result is following (can be seen in redis operator logs)
Steps to reproduce the behaviour
try installing redisfailover in openshift 3.9
Environment
How are the pieces configured?
Logs
Please, add the debugging logs. In order to be able to gather them, add
-debug
flag when running the operator.The text was updated successfully, but these errors were encountered: