Alison Holloway Senior Technical Writer & AI Consultant

Concepts Guide

Oracle Cloud Native Environment | Concepts Guide

Product:
Oracle Cloud Native Environment
Document Type:
Concepts Guide
Version:
F96190-08
Last Publish Date:
August 2025
Tools Used:
DITA XML, Oxygen XML, Git, Draw.io

Overview

The Oracle Cloud Native Environment Release 2 Concepts Guide provides comprehensive conceptual and architectural information about Oracle CNE, Oracle’s Kubernetes-based platform for cloud-native application development and management. This guide serves as the foundational reference for understanding Oracle CNE’s architecture, components, deployment models, and design principles.

Target Audience

Solution architects evaluating Oracle CNE for cloud-native projects, system administrators planning Oracle CNE deployments, platform engineers designing Kubernetes infrastructure, technical decision makers comparing platform options, and new users learning Oracle CNE fundamentals.

Key Documentation Features

Bridging Multiple Abstraction Levels

Concepts documentation must work for readers at different technical depths: high-level overview for architects and decision-makers, architectural details for system designers, and implementation concepts for administrators who will deploy systems.

Solution: Structured the guide with progressive disclosure. High-level concepts first, followed by architectural details, with clear cross-references to procedural guides for implementation specifics. Used diagrams extensively to illustrate concepts visually before diving into detailed explanations.

Multiple Deployment Models

Release 2 introduced four distinct cluster providers (libvirt, OCI, OLVM, BYO), each with different architectural implications and use cases.

Solution: Created a provider-agnostic architectural foundation, then dedicated sections for provider-specific concepts. Included architectural diagrams for each deployment model.

Documentation Approach

Conceptual Before Procedural

The Concepts Guide deliberately avoids step-by-step procedures, instead focusing on what components exist and their purposes, why architectural decisions were made, when to use different features or configurations, and how components interact at an architectural level. Procedures are referenced but kept in task-based guides.

Visual Communication

Complex distributed systems like Oracle CNE require visual explanation. The guide includes architecture diagrams showing component relationships, network topology diagrams for different providers, and data flow diagrams for key operations.

Technical Contributions

Beyond documentation, this project involved participating in architecture review sessions with engineering to ensure documentation accurately reflected system design, working with field engineers to validate that documented concepts matched real-world deployment scenarios, creating comprehensive architecture diagrams using standard notation, and coordinating with product management, engineering, and field teams to ensure conceptual accuracy.