Built from zero: eight major projects in six months.
ArgoCD GitOps on multi-tenant EKS for Ataccama’s Fortune 500 environments.
The problem
“We sold the Fortune 500 account. We have ninety days to stand up a Toronto DevOps function. We don’t have one.”
Ataccama
What was at stake
- They had closed a tier-one enterprise deal before the operational capability existed to support it.
- Releases were manual.
- The DevOps function had to be built alongside their first three production releases.
What we built
From a standing start to GitOps on every cluster.
Team, toolchain and standards first, then ArgoCD across the Fortune 500 environments.
Before · manual releases
Manual release
Production
After · a DevOps function, then GitOps on every cluster
North American DevOps function
Team structure
ToolchainTerraformAnsible
Delivery standards
Onboarding playbooks
Stood up from scratch, alongside the first three production releases.
Pull request merged
ArgoCDdeclarative, auditable, fully automated
Fortune 500 environments
AWSAzure
EKS clustermulti-tenant
Namespace ARBACQuota
Namespace BRBACQuota
Namespace CRBACQuota
EKS clustermulti-tenant
Namespace ARBACQuota
Namespace BRBACQuota
Namespace CRBACQuota
EKS clustermulti-tenant
Namespace ARBACQuota
Namespace BRBACQuota
Namespace CRBACQuota
DataDogobservability stack, written in week one
Example layout. One multi-tenant EKS cluster per Fortune 500 environment.
- 01Stood up the DevOps function: team structure, toolchain, delivery standards, onboarding playbooks.
- 02Multi-tenant EKS per Fortune 500 environment: isolated namespaces, RBAC, resource quotas.
- 03ArgoCD GitOps replaced manual releases: declarative, auditable, automated from PR merge to production.
- 04Wrote the observability stack in week one, on DataDog.
Timeline
From week one to year two.
Week oneThe observability stack is written.
Ninety daysThe client’s deadline to stand up the function, built alongside the first three production releases.
Six monthsEight major projects shipped.
Quarter fourArgoCD GitOps replaces manual releases across every client cluster.
Year twoThe same pipeline runs Ataccama’s global product.
The engagement ran 2021 to 2023.
Outcomes
What Ataccama got.
Speed
50%
faster deploys
Cost
$120k
saved per year
Mostly reserved-instance rationalization and idle cluster culls.
Delivery
8
major projects shipped in six months
Stack
EKSArgoCDTerraformAWS + AzureDataDogAnsible
Tell us what you're building.
We reply within one business day.
First call: 30 minutes, on a Tuesday or Thursday, with two engineers, not a sales rep. If we’re the wrong fit, we’ll say so and name a firm that is.