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.

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

Docker Compose to Kubernetes migration #75

Open
andrablaj opened this issue Mar 22, 2024 · 1 comment · May be fixed by #90
Open

Docker Compose to Kubernetes migration #75

andrablaj opened this issue Mar 22, 2024 · 1 comment · May be fixed by #90
Assignees
@witash
Labels
Priority: 1 - High Blocks the next release. Status: Blocked Unable to progress this. Type: Improvement Make something better
Milestone
CHT Sync Production

Comments

@andrablaj
Copy link
Member

andrablaj commented Mar 22, 2024 •
edited

From @Hareet : We requested cht-sync to be deployed / migrated to EKS a while back as we have less people to fix the automation, and maintenance required on isolated EC2 instances. We've solved that in EKS, and really want to push to utilizing that.

This seems like a perfect continuation of the effort to merge several components of the current cht-sync/cht-pipeline/dataemon setup.

Additionally, document the steps required for deploying a cht-sync instance to k3s.
@andrablaj andrablaj added the Type: Improvement Make something better label Mar 22, 2024
@witash witash self-assigned this Mar 22, 2024
@andrablaj andrablaj mentioned this issue Mar 22, 2024
Merged
@andrablaj andrablaj linked a pull request May 8, 2024 that will close this issue
Open
@andrablaj
Copy link
Member Author

@witash I noticed this ticket is moved to Done, but still open, and with no PR attached. Can you please link related PRs or explain what was done? Thank you!

@andrablaj andrablaj added the Status: Blocked Unable to progress this. label May 28, 2024
@andrablaj andrablaj added this to the CHT Sync Production milestone May 30, 2024
@andrablaj andrablaj added the Priority: 1 - High Blocks the next release. label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@witash witash

Labels
Priority: 1 - High Blocks the next release. Status: Blocked Unable to progress this. Type: Improvement Make something better
Projects
Product Team Activities
Status: Next Week's Commitments
Milestone
CHT Sync Production
Development

Successfully merging a pull request may close this issue.

helm chart for cht sync medic/cht-sync
2 participants
@witash @andrablaj