-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Multiple instances? #1155
Comments
I've deployed the upstream atlantis chart and its setup to be a stateful set with a single pvc. One pod, one read writeable storage backend. Because Atlantis uses boltdb (which lives on the pv, think sqllite) it can only be writeable by one pod, I think the way it is deployed in the chart reflects the app architecture. I dont know if there are plans to support another form of kv store/backend? But that could potentially change how many pods can run. I haven't had any issues with load yet myself rather run concurrency. |
Hi, this is not currently supported. See #894. |
What is the latest on this now? |
… On Mon, Oct 3, 2022 at 9:57 AM Dave Heward ***@***.***> wrote:
What is the latest on this now?
—
Reply to this email directly, view it on GitHub
<#1155 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3ERDWZEZE6XYYZAUE7KLWBMF6DANCNFSM4P4VVYJA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@jamengual , #1345 does not address this specific thing right? If we use the upstream helm chart for deploying Atlantis as a statefulset, and configure the number of replicas to be >1, does atlantis is able to plan/apply from the same pod? |
If you set the replica set greater than 1 then you need to use redis for locking |
right now it does, you can use the Redis external locking and share a disc between pods |
That's amazing, I did not know about that. Thanks for the quick reply |
Hello,
it is possible to run Atlantis on multiple concurrent pods with load balancing? I don't think so, but I need to confirm it.
I tried to run two pods and hide them behind NodePort just for test. Then
atlantis plan
from an merge request was processed by first pod, however followingatlantis apply
went to second pod and I've got this error message:stat /home/atlantis/.atlantis/repos/some/repo-name/1: no such file or directory
I probably understand this behaviour. Or is it my fault and there is any way to configure Atlantis to cope with this situation?
Thanks
The text was updated successfully, but these errors were encountered: