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.
@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!
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.