Kubernetes
Kubernetes and GitOps in Israel
Kubernetes clusters that behave like infrastructure rather than a research project: EKS or GKE, autoscaling, security policy, and deployments driven through git with Argo CD — including rollback with a single revert.
What the service covers
Cluster build
Amazon EKS or GKE with networking, permissions, ingress, TLS certificates and backups — all as code.
Autoscaling
Karpenter or Cluster Autoscaler sizing capacity to real load instead of guesswork.
GitOps with Argo CD
git is the source of truth: every change is a pull request, and manual drift is corrected automatically.
Safe releases
Argo Rollouts for canary and blue-green deployments, gated on real metrics.
Security and policy
namespace separation, RBAC, secrets management and image scanning before anything reaches the cluster.
Upgrades without drama
planned version upgrades, compatibility checks and a test run before production.
When Kubernetes is worth it — and when it is not
Not every system needs Kubernetes. One or two services with predictable traffic will run better and cheaper on ECS Fargate or Cloud Run. Kubernetes earns its keep when you have many services, teams releasing in parallel, variable scaling needs, or a requirement to run the same platform across clouds. If you are not there yet, I will say so on the first call.
How it works
- 1Assessment — how many services, what traffic, which security requirements, and who maintains it after handover.
- 2Cluster design — sizing, networking, permissions, estimated monthly cost and a backup plan.
- 3Build as code — Terraform for the cluster, Helm and Argo CD for the applications.
- 4Move services — one service at a time, with the option to step back at any point.
- 5Training and handover — your team learns to operate it: logs, debugging, upgrades and common failures.
Related
- DevOps and CI/CD — the pipelines that feed the cluster.
- AWS cloud services — the environment around the cluster.
- Cloud cost optimization — clusters are the number one source of waste.
- ECS or EKS — how to decide whether you need a cluster at all.
- A CI/CD platform on EKS — what it looks like in practice.
Frequently asked questions
- What does a Kubernetes cluster cost per month?
- On AWS there is a fixed charge for the managed control plane (about $70 a month for EKS), plus the compute, network and storage behind it. A small production cluster usually lands in the low hundreds of dollars a month, and proper autoscaling can cut that significantly.
- How is GitOps different from normal deployment?
- In a normal pipeline, the pipeline pushes changes into the cluster. With GitOps the cluster pulls its state from git: what is in git is what runs. That gives full history, drift detection, and rollback by reverting a commit.
- Can you take over a cluster someone else built?
- Yes, and it is a common request. It starts with a review: what was configured by hand, what is missing backups, where permissions are too broad — then the configuration moves into code step by step.
- Do we need Kubernetes to run in the cloud?
- No. Many systems run perfectly well on ECS Fargate, Cloud Run or Lambda with less maintenance and lower cost. Kubernetes is the right answer when the complexity is already there.
Tell me what you are running today
A short call, then a written plan with a cost estimate and a fixed scope. No obligation.