Study guide

5.3 OKE Workload Identity, Secrets & Persistent Storage

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

5.3 OKE Workload Identity, Secrets & Persistent Storage

Key Takeaways Explain This Topic AI

An OKE workload identity is the combination of cluster, namespace, and service account, and IAM policies match it with request.principal.type = 'workload' plus namespace, service account, and cluster ID conditions.

Oracle's open-source OCI Secrets Store CSI Driver Provider mounts Vault secrets into pods as a volume, and its periodic auto-rotation sync is disabled by default.

The OCI Block Volume CSI driver provides dynamic, high-performance ReadWriteOnce (RWO) storage with configurable dynamic performance tiers (up to 120 VPUs/GB), online volume expansion, and volume cloning.

The OCI File Storage Service (FSS) CSI driver delivers scalable ReadWriteMany (RWX) persistent storage, allowing distributed pods across multiple Fault Domains and Availability Domains to concurrently read and write to a common POSIX file system.

Last updated: October 2026

  • 4.6 OKE Workload Identity, Secrets & Persistent Storage
  • Zero-Trust Pod Security & OCI Workload Identity

Securing containerized enterprise workloads requires moving beyond host-level trust boundaries. Historically, applications running in Kubernetes obtained access to OCI resources through one of two mechanisms: embedding static OCI API signing keys inside Kubernetes Secrets, or assigning Instance Principals to the underlying worker node compute pool.

Both legacy approaches introduce severe security vulnerabilities in multi-tenant enterprise environments:

Static API Keys : Long-lived private keys stored in Kubernetes secrets or config files risk source code leakage, unauthorized exfiltration, and operational failures during manual credential rotation.

Instance Principals Blast Radius : An Instance Principal grants IAM permissions to the physical or virtual worker node. Consequently, every pod co-located on that node inherits identical administrative privileges. A compromised frontend pod can exploit the host's instance principal to access sensitive Object Storage buckets or databases intended solely for backend financial microservices.

To eliminate this structural vulnerability, OKE provides OCI Workload Identity .

How Workload Identity Works

In OCI, a workload running on an OKE cluster is treated as a resource in its own right. Its identity is the unique combination of cluster, namespace, and Kubernetes service account . You use that combination in IAM policies:

1. Prepare the Workload

Create a namespace and a Kubernetes service account, and set the deployment so every pod of the workload uses that service account. Workload identity is only available in enhanced clusters .

2. Use a Supported OCI SDK

The application authenticates with the OKE workload identity provider in an OCI SDK. Supported SDKs include Go, Java, Python, .NET, and Ruby at recent versions. Workload identity works through the SDKs; you do not use it from the Console. The provider exchanges the pod's Kubernetes service account token for a short-lived OCI token and caches it, so Oracle recommends creating one provider instance and reusing it throughout the application.

3. Write a Workload-Scoped IAM Policy

The policy uses any-user with conditions that pin it to one workload: Allow any-user to manage objects in compartment Financial-Data where all {

  • request.principal.type = 'workload',
  • request.principal.namespace = 'payments',
  • request.principal.service_account = 'payment-processor-sa',
  • request.principal.cluster_id = '<cluster-ocid>'
  • }

Including request.principal.cluster_id matters: without it, a workload with the same namespace and service account name in another cluster could match the policy. OCI Audit records the requests made by each workload identity, which supports compliance reporting.

Under this model, even if a compromised reporting pod runs on the exact same worker node as the payment processor, it cannot assume the payment processor's IAM role. Workload Identity enforces absolute cryptographic isolation at the individual pod level.

Centralized Secret Management via Secrets Store CSI & OCI Vault

Storing database credentials, API tokens, and TLS certificates directly in native Kubernetes Secret objects introduces compliance risks, as secrets are stored in etcd (often unencrypted or with basic base64 encoding unless envelope encryption is configured) and lack enterprise audit logging.

OKE integrates with OCI Vault through the Kubernetes Secrets Store CSI driver ( secrets-store.csi.k8s.io ) and Oracle's open-source OCI Secrets Store CSI Driver Provider . A SecretProviderClass lists the Vault secrets to fetch:

Volume Mounts : Secrets are retrieved from Vault when the pod starts and mounted into the container as files in a CSI volume, so they do not need to be stored as Kubernetes Secret objects in etcd.

Rotation Sync : The driver can periodically refresh mounted contents (and optionally synced Kubernetes secrets) from Vault at a configured frequency, so a secret rotated in Vault reaches running pods. This auto-rotation feature is off by default and is enabled with a Helm setting.

Encryption : Vault secrets are encrypted with a master encryption key protected by FIPS 140-2 Level 3 hardware security modules, and access is controlled with IAM policies on the secret-family resources.

Persistent Storage in OKE: Container Storage Interface (CSI) Plugins

Stateful microservices require resilient, persistent storage that survives pod recreation and worker node failure. OKE provides production-ready implementations of the Container Storage Interface (CSI) specification, supporting both block-level and file-level storage.

1. OCI Block Volume CSI Driver (ReadWriteOnce - RWO)

The OCI Block Volume CSI driver provisions high-performance, low-latency persistent block storage backed by OCI Block Volumes:

Access Mode : Operates exclusively under ReadWriteOnce (RWO) . A block volume can be formatted with a filesystem (such as ext4 or xfs ) and attached to a single worker node at any given time.

Dynamic Provisioning : StorageClasses ( oci-bv ) automate volume provisioning. When a developer submits a PersistentVolumeClaim (PVC), the CSI plugin calls the OCI Block Volume API to provision the disk and attach it via iSCSI or paravirtualized attachment to the host node.

Dynamic Performance Tiers : Architects configure storage throughput and IOPS dynamically through the vpusPerGB StorageClass parameter: 0 VPUs/GB (Low Cost) for batch logging; 10 VPUs/GB (Balanced) for general workloads; 20 VPUs/GB (High Performance) for relational databases; and 30 to 120 VPUs/GB (Ultra High Performance) delivering up to 300,000 IOPS per volume for mission-critical transactional engines.

Online Volume Expansion : Persistent volumes can be resized dynamically by editing the PVC storage request without taking the pod offline.

2. OCI File Storage Service (FSS) CSI Driver (ReadWriteMany - RWX)

The OCI File Storage Service CSI driver provides managed, highly available network file systems conforming to the POSIX specification:

Access Mode : Supports ReadWriteMany (RWX) . Multiple pods distributed across different worker nodes, different Fault Domains, and even different Availability Domains can simultaneously mount and perform concurrent reads and writes against the same shared filesystem.

Dynamic Provisioning : The oci-fss StorageClass dynamically provisions FSS file systems, export paths, and mount targets within the customer's VCN.

Mount targets : A File Storage mount target lives in a subnet and serves NFS exports. Pods on nodes in other subnets or availability domains can mount it as long as routing and security rules allow NFS traffic. For DR, File Storage replication copies a file system to another region.

Ideal Workloads : Content management systems (WordPress, Drupal), distributed machine learning datasets, shared artifact repositories, and microservices requiring concurrent write access to shared directories.

Volume Snapshots, Cloning & Backup Automation

OKE storage architecture integrates natively with OCI backup automation through Kubernetes Custom Resource Definitions (CRDs):

CSI Volume Snapshots : Developers define declarative VolumeSnapshot objects in Kubernetes. The OCI Block Volume CSI plugin captures a point-in-time, crash-consistent snapshot of the volume and stores it redundantly in OCI Object Storage.

Volume Cloning : A new PVC can specify an existing VolumeSnapshot or another PVC as its dataSource , and the CSI driver creates a new block volume from that source, which is useful for creating test copies of production data.

Storage & Security Architectural Tradeoff Matrix

Storage / Security Mechanism Primary Use Case Access Mode / Scope Latency & Performance Key Constraint

OCI Workload Identity Pod-level authentication to OCI APIs Cluster + namespace + service account Short-lived tokens cached by the OCI SDK Requires an enhanced cluster

Instance Principals Legacy host-level authentication Node-level (all pods on node share permissions) Fast (cached metadata credentials) Violates least privilege; broad blast radius

Block Volume CSI Transactional databases, single-pod state ReadWriteOnce (RWO) High IOPS, up to 120 VPUs/GB (300k IOPS) Cannot be mounted concurrently across nodes

File Storage Service CSI Shared content stores, distributed analytics ReadWriteMany (RWX) Network file system latency Mount target must be reachable over NFS

Secrets Store CSI Vault secrets mounted into pods CSI volume per pod Optional periodic rotation sync Requires the driver and the OCI provider

Loading diagram... OKE Workload Identity & CSI Storage Architecture