Detailed instructions to setup a Kubernetes (EKS and GKE) CI/CD pipeline
Budget: €100 – €400 EUR
We want to be able to setup a CI/CD pipeline for our GitHub projects. We have Kubernetes clusters running on EKS and GKE and we want a CI/CD solution where we will do a PR in Github and then the project is going to be deployed to the EKS and GKE clusters.
We are open to multiple approaches (using Jenkins, Github Actions, Docker Hub, TeamCity or whatever free or paid solution) obviously the lower the monthly cost of the solution the better. Please quote whatever approach you propose and the deliverable will be detailed instructions we can use to setup the pipeline for both EKS and GKE clusters. Security should be taken into account. The connection with the EKS and GKE clusters needs to happen using best practices (e.g. basic auth is deprecated in GKE and should not be used) and also application environment secrets need to be managed appropriately.
We are open to multiple approaches (using Jenkins, Github Actions, Docker Hub, TeamCity or whatever free or paid solution) obviously the lower the monthly cost of the solution the better. Please quote whatever approach you propose and the deliverable will be detailed instructions we can use to setup the pipeline for both EKS and GKE clusters. Security should be taken into account. The connection with the EKS and GKE clusters needs to happen using best practices (e.g. basic auth is deprecated in GKE and should not be used) and also application environment secrets need to be managed appropriately.