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

New helm chart for playbooks #56

Open
robkooper opened this issue Apr 20, 2023 · 0 comments
Open

New helm chart for playbooks #56

robkooper opened this issue Apr 20, 2023 · 0 comments
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem devops
Milestone

Comments

@robkooper
Copy link
Member

Create a new helm chart that would allow us to deploy playbooks independently. Each deployment will have their own values that get deployed. So we would deploy this helm chart 3 times:

  • SLC
  • Joplin
  • Galveston

Helm chart will have following components:

  • playbook (required)
  • maestro (required)
  • database (optional)
  • datawolf (optional)

We can deploy this in a new cluster/namespace and control the resources for that cluster/namespace.

@longshuicy longshuicy added this to the Workshop 4 milestone Feb 19, 2024
@longshuicy longshuicy changed the title new helm chart for playbooks New helm chart for playbooks Feb 19, 2024
@longshuicy longshuicy added the 3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem devops
Projects
None yet
Development

No branches or pull requests

3 participants