Services
Docker, Kubernetes, and Argo CD
Docker is the box, Kubernetes is where it runs, and Argo CD is how a reviewed commit reaches the cluster. We add them when the team is ready to operate them.
The three pieces are one delivery path. An image nobody can rebuild, or a cluster only one person understands, is not the goal.
When it fits
- Deploys depend on one server or one person.
- The app is not in a container yet, or nobody can rebuild the image.
- You want a merge in Git to be what goes live.
How the work goes
- The Dockerfile is small, pinned, and built the same way in CI.
- We name what belongs in the image and what stays in config.
- Kubernetes manifests match the way you already deploy, for one environment first.
- Argo CD watches the repository, so a merge is what rolls forward, and a revert is a commit.
Example: follow the commit
Rollout
Drag an item onto a row, or select it and use the Move buttons.
Drag the commit from the image to the cluster, then to Argo CD.
Image
Cluster
Argo CD
Move
What you receive
- An image the pipeline can rebuild tomorrow
- Manifests for one environment the team can explain
- Argo CD pointing at Git, with a rollback that is a commit
How to start
Send how the app is deployed today and where it should run. Email it to info@developerlab.nl, or see the contact page for other ways to reach Puya Sarmidani.
Send an email