I am looking to implement a CICD a solution that permits deployment to multiple environments (AWS EKS) when a change to a specific branch is committed, this can be easily achieved if I have a single repository of course but in my scenario I have multiple microservices in different repositories that I wish to deploy to the same collection of environments and I'd rather not have to recreate the environment for each microservice or if I add a new environment have to update all my repositories.
What is the best / recommended way to achieve this?
Hey @Marc Benson
I suggest to have a dedicated repo for mapping each env to the relevant micro-service and its version. This repo would also hold the needed files for your selected deployment tool.
Once you have that, you need a CD pipeline to identify the change and update the version accordingly. IE, the specific branch you would be listening to in order to trigger the deployment, would be from the new repo.
Since you are working with K8s, there are plenty of tools out there, such as argoCD, Helm, Harness, Ansible and more.
Note - the tools above are just the ones I've crossed path with. There are probably more, and even better tools for what you need. Google would be your friend here :)
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.