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.

Sign up for GitHub

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

Jump to bottom

separate k8s deployments and implement a linking service #6

Open

dperl-dls opened this issue Jun 7, 2024 · 0 comments

Collaborator

dperl-dls commented Jun 7, 2024 •

edited

Loading

To conform to best practises we should have one container per deployment, and a service to allow the backend to talk to the database.

This should "just work" both for local, dev (pollux) and prod (argus) deployments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment