CI/CD pipelines and GitOps
A CI/CD pipeline builds, tests and deploys your software the same way every time, without depending on anyone's memory. GitOps goes a step further: what runs in production is whatever is in the repository.
I'm a CI/CD consultant in London. I build and repair pipelines in GitLab CI and Jenkins, and run GitOps with Argo CD and FluxCD.
What I do
- Build a pipeline where there is none. From a deployment done by hand to one anyone on the team can run.
- Repair slow or unreliable pipelines, so deployments are quick and dependable.
- Separate the environments, so a change meant for development cannot reach production by accident.
- GitOps for Kubernetes with Argo CD or FluxCD, and Helm charts your developers can edit.
- Terraform through the pipeline with Atlantis, so infrastructure changes are reviewed like code.
- Smaller, faster Docker builds.
- Secrets out of the pipeline and into HashiCorp Vault.
What I'd look at first
- How long a deployment takes, and how often it fails.
- Whether there is a tested way back to the previous version.
- Where the credentials live.
- Whether a change to one environment can touch another.
What it costs
Writing down how you release today, and what it would take to automate, is a small job, from £500. Building or repairing the pipeline itself gets a fixed price, agreed in writing.
I take on CI/CD work as an ad hoc job, fractional DevOps days each month, a contract or an audit, on site or remotely across the UK. I write about infrastructure at hamzahkhan.com. Get in touch.