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

Deploy/use central secret storage #38

Open
pat-s opened this issue Jan 30, 2024 · 2 comments
Open

Deploy/use central secret storage #38

pat-s opened this issue Jan 30, 2024 · 2 comments

Comments

@pat-s
Copy link
Contributor

pat-s commented Jan 30, 2024

E.g. https://github.com/Infisical/infisical

@anbraten
Copy link
Member

We currently use an encrypted file to store secrets. This currently has the huge benefit for us that it does not need a server as our infrastructure is pretty minimal using a single server. If this server would also hosts tools to deploy itself, it could easily bring us into chicken-egg situations, I guess. The same thing somehow applies to #36.

@pat-s
Copy link
Contributor Author

pat-s commented Jan 31, 2024

Only HA (partly) solves the chicken/egg problem. And event there, some initial state must be provisioned manually once.

In case of failures of the central deployment app or secret storage, you always have local ssh access or backups to bring this one back up. These are then of course essential and required to provision all the rest.

Backups is actually a topic on its own. The cheapest way is to rsync the persistent data to s3. The combination of the above provides a robust architecture which can be restored manually in case of unforeseen events.

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