You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding the flag "-n NAMESPACE" to the deployment I got it to start, but it seems like it still tries to access resources at the cluster scope (jobs.batch):
time="2020-01-16T03:29:34Z" level=info msg="Using namespace XXXXXX"
time="2020-01-16T03:29:34Z" level=info msg="Creating event broadcaster"
time="2020-01-16T03:29:34Z" level=info msg="Setting up event handlers"
time="2020-01-16T03:29:34Z" level=info msg="Setting up experiments event handlers"
time="2020-01-16T03:29:34Z" level=info msg="Setting up analysis event handlers"
time="2020-01-16T03:29:34Z" level=info msg="Waiting for controller's informer caches to sync"
E0116 03:29:34.439801 1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1.Job: jobs.batch is forbidden: User "system:serviceaccount:XXX:argo-rollouts" cannot list resource "jobs" in API group "batch" at the cluster scope
E0116 03:29:35.441056 1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1.Job: jobs.batch is forbidden: User "system:serviceaccount:XXXX:argo-rollouts" cannot list resource "jobs" in API group "batch" at the cluster scope
E0116 03:29:36.442245 1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1.Job: jobs.batch is forbidden: User "system:serviceaccount:XXX:argo-rollouts" cannot list resource "jobs" in API group "batch" at the cluster scope
E0116 03:29:37.443539 1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1.Job: jobs.batch is forbidden: User "system:serviceaccount:XXX:argo-rollouts" cannot list resource "jobs" in API group "batch" at the cluster scope
The text was updated successfully, but these errors were encountered:
Hi,
I've deployed argo rollouts using the namespace-install.yaml (https://github.com/argoproj/argo-rollouts/blob/v0.6.2/manifests/namespace-install.yaml).
After adding the flag "-n NAMESPACE" to the deployment I got it to start, but it seems like it still tries to access resources at the cluster scope (jobs.batch):
The text was updated successfully, but these errors were encountered: