-
Notifications
You must be signed in to change notification settings - Fork 176
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
What's the correct way to deploy Concourse as a Deployment
instead of StatefulSet
#255
Comments
I think you probably have a few things wrong in your deployment. I'll give you a few pointers here that hopefully help. First, I'm not sure if this was some typo or bad copy-paste on your end, but from your codeblock, the For the |
You need to configure an additional volume to get it to work as "Deployment", add to your values.yml file something like this:
I guess the chart could be "smarter" and do this automatically when you switch to kind "Deployment" |
Thank you very much @yatzek . I was completely stumped on this for a bit as I assumed the Chart would handle any additional volume configuration as a result of using Deployment workers. The docs here are definitely lacking on what using a Deployment worker looks like. I'll look into creating an issue overviewing our setup configuration to have all of this info in one place for future Googlers. |
I tried configuring Concourse to use a deployment
but saw a number of errors on the workers as well as in the UI
find or create container on worker concourse-worker-786c4bdc76-ggxzt: failed to create volume
What's the correct way to deploy Concourse as a
Deployment
instead of StatefulSetThe text was updated successfully, but these errors were encountered: