Kevin Falting03/02/2023, 8:04 PM
Mike Lee03/02/2023, 8:43 PM
Then to generate the complete configuration we had an ArgoCD Application that would run `kustomize build` on the overlay that corresponded with the target service & environment being deployed. This was only configuration though; secrets were being managed in Hashicorp Vault and the Vault Agent injector.
/service-x /deployment /base kustomization.yaml deployment.yaml service.yaml config.yaml /overlays /development kustomization.yaml config.yaml /staging kustomization.yaml config.yaml /production kustomization.yaml config.yaml
yourself and commit the Kubernetes manifests that are built to a single Github repository that contains the manifests for all of your services. That is to put the Kustomize “templates” into each service’s repository:
Then have the CI run
# repo service-x /service-x /deployment /base/... /overlays /development/... /staging/... /production/... # repo service-y /service-y /deployment /base/... /overlays /development/... /staging/... /production/...
on them and dump the complete manifests to a central repository for all services.
This is only one way though and I’m curious to hear how others have done it.
# repo service-deployments /service-deployments /service-x /development/manifest.yaml /staging/manifest.yaml /production/manifest.yaml /service-y /development/manifest.yaml /staging/manifest.yaml /production/manifest.yaml
Asaf Erlich03/02/2023, 10:42 PM
Kush Shah03/02/2023, 11:22 PM
Kevin Falting03/03/2023, 11:50 PM
Dayuan Li03/09/2023, 9:02 AM