Kubernetes across AWS and private infrastructure
Kubernetes needs ongoing upgrades, capacity planning, node management, and security reviews. DJ2 Services designs and operates clusters across Amazon Elastic Kubernetes Service (EKS) and private infrastructure. The same engineering team handles AWS and colocation clusters using consistent platform standards.
Application teams own their deployments. DJ2S covers the underlying platform, including updates, policy configuration, backups, and recovery procedures.
What we handle around the cluster
Design the AWS accounts, networking, identity, and access controls around EKS as part of your wider infrastructure.
Run Kubernetes on infrastructure you own. For environments with virtual machines and containers, OneKS can provision clusters through the OpenNebula control plane.
Plan upgrades, node capacity, and admission policies. Use Terraform and Ansible to make platform changes repeatable.
Decide where Kubernetes belongs
- Workload placement: the diagnostic assesses which workloads need Kubernetes and which can run as virtual machines. Those requirements determine the smallest suitable platform.
- Application deployment: software vendors can use Kubernetes as a common layer across EKS, OneKS, and customer-owned clusters.
- Responsibilities: application ownership stays with you. We handle agreed platform work under a capped retainer. General help-desk support is outside the scope.
What an architecture review covers
- Where clusters run, their versions, and the systems they depend on
- Identity, network boundaries, and policies across environments
- Upgrade and node plans with a schedule for version changes
- Platform backups, recovery procedures, and evidence for security reviews
DJ2 Services (DJ2S) builds, secures, and operates hybrid infrastructure across AWS, colocation, private compute, and Kubernetes. Hardware and cloud accounts remain customer-owned.