Access and traffic
For the selected themes, inspect relevant cluster or workload identities, RBAC, traffic controls and secrets handling.
Cloud platforms · 01 · The problem and the decision
Kubernetes production-readiness reviewWhat happens to the cluster if that engineer leaves?
The cluster is running, but incidents repeat and critical knowledge sits with one person. Focus on the agreed readiness questions in one cluster before a launch, a handover or the next round of growth.
For Heads of Platform and MSP delivery teams responsible for AKS, EKS or GKE.
2 weeks elapsedOne agreed AKS, EKS or GKE cluster; selected readiness themesA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
Agree the readiness themes and depth needed for your next decision. The proposal selects the areas below and the evidence to inspect within one cluster and its relevant delivery paths.
Delivery and capacity
Review the agreed manifests and delivery evidence for questions such as resource settings, upgrades or rollback.
Operations and recovery
Where selected, inspect existing alert, backup, restore or runbook evidence and the responsibilities of the inheriting team.
What we need from you
- Read access to the agreed cluster and the manifests, pipelines and operational evidence relevant to the selected themes.
- A named platform owner and an agreed list of workload paths to inspect.
- Existing incident, recovery and change records where available.
Scope and boundaries
- Penetration testing, disruptive failover, production changes and a full review of every cluster control are outside the entry scope.
- Additional clusters, deeper testing, hardening implementation and detailed implementation-ticket engineering are separately scoped.
03 · What you get
A decision you can act on.
- Findings for the selected readiness themes, linked to available manifests, policies or operational evidence.
- A prioritised action list with suggested owners.
- A decision record showing what the review supports, what remains untested and which gaps affect the next milestone.
- A read-out with the platform owner and the team responsible for the next actions.
04 · Relevant work and a sample
See the thinking behind the review.
An assessment grounded in the Azure estate
For a Dutch municipality, through Infield ICT, Atsky assessed an AKS landing zone built on Bicep and Azure DevOps. Resource Graph and Traffic Analytics supplied evidence for the findings. The engagement also included an AKS enablement programme for the team inheriting the platform.
05 · Duration and price
A defined engagement. An agreed scope.
From €7,500Starting price, excluding VAT
From €7,500, excluding VAT, for a focused review of one agreed cluster and selected themes. We quote a fixed fee after agreeing the workload inventory, access and review depth. Two weeks is an elapsed delivery window, confirmed around the required inputs. Additional clusters, deeper testing, remediation and detailed implementation-ticket engineering are separate.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
- Duration
- 2 weeks elapsed
- Base scope
- One agreed AKS, EKS or GKE cluster; selected readiness themes
- Your data
- Read-only access, in a workspace that holds only your engagement. If your policy requires it, we work with EU-only processing and zero data retention. Any extra cost is named in the proposal.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, discuss the production milestone, recurring incidents or handover concern. Review the cluster inventory and agree the evidence needed for a useful readiness decision.
This requests a 45-minute conversation. We confirm a suitable time with you.
Are the main questions about the wider cloud estate, identity or landing-zone controls? Start with the landing-zone assessment.