Move from first run to platform readiness with Oracle Database Operator for Kubernetes

Key insights

• A healthy one SingleInstanceDatabase is useful evidence, not a production permit. It shows that Oracle Database Operator for Kubernetes has aligned the stated intent enough to report the observed status.

• The custom resource is the operating contract for operator-managed intent, but storage, images, secrets, access, networking, observability, cleansing, recovery, and support remain the responsibility of the platform.

• Use read-only kubectl Inspection to create a readiness inventory. For each signal, document what the cluster shows, what that signal supports, and what remains unvalidated.

• Keep backup, restore, HA, patching, and upgrades as separate validation tracks. A successful first pass is not evidence of recovery objectives, failover behavior, or maintenance security.

A healthy custom resource is not a production decision

The first run worked. The freedb-lite-sample SingleInstanceDatabase reconciled. The database pod appeared, memory was bound, and the workload had…