Is it possible not to run argo in the "argo-rollouts" namespace? #1148
Answered
by
jessesuen
bahramrushenas
asked this question in
Q&A
-
We have not been successful in configuring argo-rollouts to run in a different namespace than "argo-rollouts". Is that even possible? Thank you |
Beta Was this translation helpful? Give feedback.
Answered by
jessesuen
May 18, 2021
Replies: 1 comment
-
Yes, it should be possible. I assume you must be getting permission problems. You will need need to adjust the ClusterRoleBinding to reference the namespace of the new location. e.g.: apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: argo-rollouts-clusterrolebinding
labels:
app.kubernetes.io/component: rollouts-controller
app.kubernetes.io/name: argo-rollouts-clusterrolebinding
app.kubernetes.io/part-of: argo-rollouts
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: argo-rollouts-clusterrole
subjects:
- kind: ServiceAccount
name: argo-rollouts
namespace: DIFFERENT-NAMESPACE # <<<<< change this |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
jessesuen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, it should be possible. I assume you must be getting permission problems. You will need need to adjust the ClusterRoleBinding to reference the namespace of the new location. e.g.: