DoD IL5 Kubernetes on OCI OKE delivers the agility, security and cost control legacy mission platforms lack.

Across the Department of Defense (DoD), mission systems continue to depend on legacy, non‑containerized environments running on virtual machines or even bare‑metal servers. These platforms sustain critical operations, but they also limit scalability, slow innovation, and increase operating costs.

SRG IL5 Kubernetes with OCI OKE changes that dynamic. Acting as a “cloud operating system,” Kubernetes abstracts away the underlying infrastructure so teams can deploy and manage applications consistently and securely across clouds.

On Oracle Cloud Infrastructure (OCI), Kubernetes provides the foundation for secure modernization of mission‑critical workloads. 

With Kubernetes, developers define what the system should do—not how to build it.

Declarative manifests describe desired states, such as a service of type “LoadBalancer.” (More details on LoadBalancer Type). On Oracle Cloud Infrastructure (OCI), Kubernetes automatically provisions an OCI Load Balancer to fulfill that request.

This abstraction enables portability and interoperability, making multi‑cloud strategies feasible for federal missions. For the DoD, it offers agility and flexibility without compromising security or compliance. 

Containers package an application, its dependencies, and configuration into a single immutable image. This guarantees that the same version runs identically in every environment—from development to production.

By generating and maintaining a Software Bill of Materials (SBOM), teams know precisely what is running, strengthening both cybersecurity and configuration assurance. 
 
Traditional VM environments cannot deliver that same consistency. Updates or patching routines often introduce unexpected changes, creating drift between development, test, and production environments.

Containers eliminate that uncertainty, providing immutability and repeatability—two attributes vital to mission assurance. 

Kubernetes enables greater resource efficiency by allowing multiple containers to share a single virtual machine while maintaining workload isolation.

This means higher utilization of compute resources and lower overall infrastructure costs—critical for defense programs that must balance mission performance with budget discipline. 
 
Legacy VM setups often run multiple applications on a single host, risking dependency conflicts. Containers eliminate this issue by isolating each application. The result is higher performance, predictable scaling, and streamlined maintenance across mission platforms. 

Without Kubernetes, federal and defense agencies face recurring challenges: development environments rarely match production, deployments are slow, and system drift increases security risk.

Legacy stacks rely heavily on manual patching and system administration, making it difficult to ensure reproducibility and reliability. 
 
Some older applications—particularly those built in early Java environments—once struggled to manage resource limits when moved from bare metal or VMs into containers, sometimes exhausting CPU or memory.

Although these issues have since been resolved, they underscore the need for modernization. More broadly, adopting Kubernetes requires a cultural shift: moving from managing servers to managing code, containers, and automation pipelines. 

Without Kubernetes, federal and defense agencies face recurring challenges: development environments rarely match production, deployments are slow, and system drift increases security risk.

Legacy stacks rely heavily on manual patching and system administration, making it difficult to ensure reproducibility and reliability. 
 
Some older applications—particularly those built in early Java environments—once struggled to manage resource limits when moved from bare metal or VMs into containers, sometimes exhausting CPU or memory.

Although these issues have since been resolved, they underscore the need for modernization. More broadly, adopting Kubernetes requires a cultural shift: moving from managing servers to managing code, containers, and automation pipelines. 

Oracle Cloud Infrastructure provides a managed Kubernetes service called Oracle Container Engine for Kubernetes (OKE).  

OKE manages the control plane—the component responsible for scheduling, scaling, and maintaining the cluster—while users manage worker nodes and workloads. This division of responsibility allows DoD mission teams to focus on application resilience and security rather than low‑level platform maintenance. 
 
For organizations adopting Kubernetes for the first time, OKE provides the reliability, scalability, and automation needed to meet mission‑critical requirements while maintaining compliance with federal standards.  More information about OKE concepts can be found here.

Ikeda Innovations (2i) has deployed numerous mission‑critical services—such as Apache NiFi, Jenkins, JFrog Artifactory, and Apache Guacamole—on Oracle Cloud Infrastructure using Kubernetes.

The objective: to containerize as many common services as possible for speed, consistency, and security. 
 
Most workloads run on Linux, the preferred OS for container environments because of its light footprint and flexibility. Early in deployment, the team discovered circular dependencies while using Artifactory as both a registry and image source.

The solution was to mirror images to Oracle Container Registry, which proved highly reliable across OCI regions and simplified upgrades. 

Many federal customers also operate workloads on AWS (EKS) or Azure (AKS).

While each provider offers similar Kubernetes capabilities, OCI often stands out for cost efficiency, predictable pricing, and data‑egress structure. For data‑intensive DoD workloads—such as telemetry processing or cyber defense analytics—these cost and performance advantages compound at scale. 
 
Beyond cost, OCI’s integration with Oracle Database services, native IAM, and security boundary controls makes it well‑suited for high‑assurance environments that demand both compliance and performance. 

While OKE manages the Kubernetes control plane, 2i customizes the environment for mission‑specific compliance and security. This includes network isolation, least‑privilege configurations, and private control‑plane endpoints shielded from public access.

These enhancements harden the cluster against intrusion while maintaining high availability. 
 
OCI’s architecture enables 2i to layer additional security controls at the node and application levels, aligning with FedRAMP High and DoD SRG IL5 guidelines. These configurations ensure that workloads remain both secure and efficient in classified and unclassified environments. 

Once the platform is operational, observability becomes the foundation of mission assurance.

Kubernetes provides readiness and liveness probes to restart unhealthy services automatically, but 2i extends this with advanced telemetry through Prometheus, Grafana, and OCI Monitoring. These tools track latency, resource utilization, and error rates, giving teams full visibility into application health and performance. 
 
For ongoing security posture management, 2i integrates continuous vulnerability scanning and image validation pipelines. This ensures compliance with federal DevSecOps practices while reducing mean time to detection and response. 
 

The results of Kubernetes adoption on OCI have been measurable and repeatable.  

With containerized architectures, 2i can patch vulnerabilities and roll out new versions in hours rather than weeks. Applications recover faster and achieve near‑continuous availability. Customers have praised 2i’s rapid response and system reliability, especially when meeting time‑sensitive DoD milestones. 
 
Even when end users are not deeply familiar with Kubernetes, they recognize the difference: improved performance, higher availability, and faster turnaround times. These outcomes translate directly into greater mission resilience and operational readiness. 

OCI’s managed Kubernetes service—combined with 2i’s engineering expertise—provides a secure, efficient, and maintainable foundation for DoD mission systems. Once configured, the environment supports continuous modernization, compliance monitoring, and mission readiness. 
 
By leveraging OCI’s cost advantages and 2i’s proven containerization methods, federal teams achieve faster delivery, stronger cybersecurity, and higher resilience. Together, these capabilities create a sustainable, secure container platform purpose‑built for defense modernization. 

Explore our suite of services or dive into the experts insights below. You will discover how we help federal teams modernize, protect, and accelerate their missions.