-
Notifications
You must be signed in to change notification settings - Fork 344
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
Operator cannot create resources in other namespaces even in cluster-wide mode #931
Comments
I have a workaround for this, but looks like the problem is underneath our operator, either at the SDK, controller-runtime or perhaps even client-go. |
There are actually a couple of problems happening here:
The problem you reported is most likely the first item, so, I'll change the title back to that and create a new one to track the second problem. |
The issue still exists in latest version. I'm using chart 2.21.1 with image 1.22.1, I've set the following options: rbac:
create: true
clusterRole: true But I still see this log message: But when I add This is the role that helm has generated: ---
# Source: jaeger-operator/templates/role.yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: jaeger-operator
namespace: {{ .Release.Namespace }}
labels:
app.kubernetes.io/name: jaeger-operator
rules:
- apiGroups:
- ""
resources:
- pods
- services
- endpoints
- persistentvolumeclaims
- events
- configmaps
- secrets
- serviceaccounts
verbs:
- '*'
- apiGroups:
- apps
resources:
- deployments
- daemonsets
- replicasets
- statefulsets
verbs:
- '*'
- apiGroups:
- networking.k8s.io
resources:
- ingresses
verbs:
- '*'
- apiGroups:
- monitoring.coreos.com
resources:
- servicemonitors
verbs:
- get
- create
- apiGroups:
- io.jaegertracing
resources:
- '*'
verbs:
- '*'
- apiGroups:
- extensions
resources:
- replicasets
- deployments
- daemonsets
- statefulsets
- ingresses
verbs:
- "*"
- apiGroups:
- batch
resources:
- jobs
- cronjobs
verbs:
- "*"
- apiGroups:
- route.openshift.io
resources:
- routes
verbs:
- "*"
- apiGroups:
- logging.openshift.io
resources:
- elasticsearches
verbs:
- '*'
- apiGroups:
- jaegertracing.io
resources:
- '*'
verbs:
- '*'
- apiGroups:
- rbac.authorization.k8s.io
resources:
- clusterrolebindings
verbs:
- '*'
- apiGroups:
- apps
- extensions
resourceNames:
- jaeger-operator
resources:
- deployments/finalizers
verbs:
- update
- apiGroups:
- kafka.strimzi.io
resources:
- kafkas
- kafkausers
verbs:
- '*'
- apiGroups:
- autoscaling
resources:
- horizontalpodautoscalers
verbs:
- '*' |
After PR #928 I have not been able to install an operator that works cluster-wide. It's possible I am not following the updated instructions correctly, but here is what I did:
(Note the last line uses my modified version of operator.yaml)
The operator appears to install correctly, but when I do the following:
I get the following errors in the jaeger operator log. (Actually I get them repeatedly, as in 1 a second.)
This occurs both on minikube and on Openshift
The text was updated successfully, but these errors were encountered: