-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Argo server should start without configmap #2285
Labels
Milestone
Comments
sarabala1979
added a commit
to sarabala1979/argo
that referenced
this issue
Feb 21, 2020
5 tasks
sarabala1979
added a commit
that referenced
this issue
Feb 21, 2020
Saw this bug again in 2.7.0
|
alexec
added
the
type/regression
Regression from previous behavior (a specific type of bug)
label
Apr 1, 2020
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Apr 1, 2020
5 tasks
alexec
added a commit
that referenced
this issue
Apr 2, 2020
alexec
added a commit
that referenced
this issue
Apr 2, 2020
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What happened:
If the workflow-controller is running in a cluster scope, the user can submit the workflow from their namespace. The user wants to run the argo server in hosted/local mode for their namespace. They don't enable persistence and they don't have permission for Argo namespace. Argo server is throwing below error.
What you expected to happen:
Argo server can start without
workflow-controller-configmap
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
Logs
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: