-
Notifications
You must be signed in to change notification settings - Fork 888
chore: setup dev.coder.com with multiple coderd instances #8043
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
Comments
We should be using Kubernetes as our dogfood as well. VM as control plane and docker workspaces is not what the majority of enterprise customers are using. |
We can also explore using docker-compose with multiple replicas to keep things simple. I can do this if we agree. |
Docker compose is fine with me as long as we have a multi-replica setup. |
@deansheather @ammario, do you have any preferences? |
Sounds fine to me |
We now have multiple coderd replicas along with external provisioners. |
We should be running our dogfood deployment with multiple Coderd instances so that we are regularly exercising the "distributed" versions of our code.
There is no requirement to locate these instances in different availability zones, as the motivation is not to increase availability of our own service. E.g. running them in 2 Docker containers on the same host is fine.
The text was updated successfully, but these errors were encountered: