Oracle Container Engine for Kubernetes (OKE) is Stable from Word Go

Kubernetes has now become premier de-facto standard for orchestration of containers. A whole new community has built up around it and growing by the day. Oracle has ramped up its Kubernetes offering in the shape of managed Kubernetes service OKE, which is stable from the word go.

OKE is mature and battle tested to orchestrate containerized applications at scale while reducing the time, cost, and operational burden of managing the complexities of Kubernetes infrastructure. Container Engine for Kubernetes enables you to deploy Kubernetes clusters instantly and ensure reliable operations with automatic updates, patching, scaling and new features are being added every day.

Oracle manages the control plane where as two types of worker nodes can be used in OKE:

• Managed nodes are Oracle Cloud Infrastructure (OCI) Compute instances that you configure and manage as needed.
• Virtual nodes deliver a serverless Kubernetes experience, enabling you to ensure reliable operations at scale without the operational overhead of managing, scaling, upgrading, and troubleshooting the infrastructure of your clusters.

By understanding the concepts of availability domains, node labels, Anti-Affinity and TopologySpreadConstraints, you can distribute pods of a deployment across different availability domains or faults domains within an OKE cluster. Another cool feature of OKE is solid observability. Oracle Cloud Infrastructure, Datadog, Aqua Security can be used to monitor OKE in a seamless fashion.

One other feature I love about OKE is that you can safely delete a node and OKE automatically drains and cordons off the node. This doesn't disrupt your application at all. I have tried it in different scenarios and not even once my application failed. 

You can also use your own tooling for security, federation, observability, and build automation.