GitOpsPlatform
GitOps deployments with multi-image Kustomize
- Company
- Adeva — Fashion Digital client
- Role
- Senior Site Reliability Engineer
- Period at the company
- Sep 2025 — Present
Problem
Team’s GitOps tooling assumed one image per deployment and microservice versions weren’t updated in real time, so multi-container services couldn’t be rolled out granularly and rollout signal from GitHub lagged behind what was actually merged.
Approach
Deployment application’s Kustomize usage was refactored to support multiple images inside a single deployment manifest. Polling logic was reworked with webhooks, allowing more frequent updates to be pulled from GitHub history instead of a slow scheduled sync.
Impact
- Multi-container services were reworked to be presented without workarounds.
- Deployment status reflects GitHub history far closer to real time.
Tech stack
ArgoCDKustomizeKubernetesGitHub