What is actually wrong with your platform?
Three days inside your tenancy, quotas, secrets delivery, and access, ending in a written list ranked by how much each item will hurt.
$15,000 · three days, and the written report
The question
Find out what is actually wrong before you fund the fix.
Three days go through your platform: how your tenancy is put together, where quotas and namespaces are loose enough to matter, how secrets get to the workloads that need them, and what happens to everyone else when one thing breaks.
What you get
A written list, ordered by how much it will hurt and ranked so you know what to do first.
If nothing serious turns up, I will tell you that instead of selling you something.
How it runs
The three days cover five things.
- Tenancy and isolation. How your tenants are separated, and what one of them can do to the others on a bad day.
- Quotas and namespaces. Where limits are loose enough that one workload can starve the rest.
- Secrets delivery. How secrets reach the workloads that need them, and who else can read them on the way.
- Access and RBAC. Who can do what, and who no longer should.
- When one thing breaks. What else goes down with it, and who finds out first.
Price and timing
- Price
- $15,000 for the three days and the written report.
- Time
- Three days.
- Toward a build
- These three days come off the price of a build if you book within sixty days.
Who does the work
Douglas Adolph. I designed and built the deployment system behind a fleet of thousands of production Kubernetes clusters at a Fortune 50 company, and took deployments to that fleet from weeks down to seconds, and I still maintain it today. Around it I have written the controllers that keep a fleet honest, the authentication path teams use to reach clusters at all, the secrets tooling, and the post-deploy verification that catches a release which reconciled cleanly and is quietly unhealthy.
The engineer who scopes your work is the engineer who does it.
Longer background, and the public code I own, at douglasadolph.com. Read the source before you talk to me.
Send me the problem
Tell me what you are trying to find out and I will tell you whether I can help, including when the answer is that you do not need me.
- What is stuck, or what you are trying to measure.
- What you have already tried, and what happened.
- Any date you are working against.
A short note beats a long form. What comes back is a reply from me rather than a scheduling link, which engagement fits or that none of them does, and for a build, a scope and a number before you owe anything.