Skip to content
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

pritunl: Mongo should be a statefulset as well #1

Open
victortrac opened this issue Oct 24, 2019 · 2 comments
Open

pritunl: Mongo should be a statefulset as well #1

victortrac opened this issue Oct 24, 2019 · 2 comments
Assignees

Comments

@victortrac
Copy link
Member

We can't have more than 1 mongo, since we might as well put it in a StatefulSet. We should also rename replica_set.yaml and statefulset.yaml to just be what they are for: mongo.yaml and pritunl.yaml or whatever and then put in the resources required for each in the same file. That's clearer what the purpose is than the resource-type file names.

@techmexdev
Copy link

Renamed pritunl templates dir files: 3638879, and changed mongo to StatefulSet: 778db0a

@victortrac
Copy link
Member Author

@rodolfo-r Have you tested this from scratch? Ideally, from a clean cluster like cloudkite-dev, we 1) delete the pritunl namespace 2) test tihs chart 3) delete the pods and see how they recover. Also, for public things like helm charts, we definitely should do PRs instead of simply merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants