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

Prepare deployable application skeleton (app + db) #79

Closed
pnpavlov opened this issue Jul 1, 2024 · 2 comments
Closed

Prepare deployable application skeleton (app + db) #79

pnpavlov opened this issue Jul 1, 2024 · 2 comments
Milestone

Comments

@pnpavlov
Copy link
Member

pnpavlov commented Jul 1, 2024

Package all required components of the GLVD backend in a deployment manifest that can be applied to a Kubernetes environment. That includes but is not limited to:

  • Helm charts for the GLVD API and for the database deployed in same namespace.
  • The components of the chart need to decoupled in a way that enables managing them separately and exposing them within the environment over services. For now we can assume it's single namespace.

Not in scope:

  • No High Availability or Disaster Recovery requirements to be covered during this early development stage.
@pnpavlov pnpavlov changed the title Application skeleton deployable in the cluster (app + db) Prepare deployable application skeleton (app + db) Jul 1, 2024
@pnpavlov pnpavlov added this to the 2024-08 milestone Jul 25, 2024
@pnpavlov pnpavlov modified the milestones: 2024-08, 2024-09 Sep 4, 2024
@pnpavlov
Copy link
Member Author

pnpavlov commented Feb 4, 2025

@fwilhe , can you please confirm this is done and can be closed? Do we have a deployment manifest with or without helm that could be referred to? If so, please refer and close?

@fwilhe
Copy link
Member

fwilhe commented Feb 4, 2025

Yes we have a working k8s deployment here. Did not convert this to helm so far because I don't think it would bring us a huge benefit, but @MrBatschner already sketched out what this would look like. It is a question of priority, and for me this has close to zero priority currently because the existing solution works well enough for now.

@fwilhe fwilhe closed this as completed Feb 4, 2025
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