The WebLogic Kubernetes Operator supports deployment of Oracle Access Management (OAM).

In this release, OAM domains are supported using the “domain on a persistent volume” model only, where the domain home is located in a persistent volume (PV).

The WebLogic Kubernetes Operator has several key features to assist you with deploying and managing Oracle Access Management domains in a Kubernetes environment. You can:

  • Create OAM instances in a Kubernetes persistent volume. This persistent volume can reside in an NFS file system or other Kubernetes volume types.
  • Start servers based on declarative startup parameters and desired states.
  • Expose the OAM Services through external access.
  • Scale OAM domains by starting and stopping Managed Servers on demand.
  • Publish operator and WebLogic Server logs into Elasticsearch and interact with them in Kibana.
  • Monitor the OAM instance using Prometheus and Grafana.

Current production release

The current production release for the Oracle Access Management domain deployment on Kubernetes is 23.2.1. This release uses the WebLogic Kubernetes Operator version 4.0.4.

For 3.4.X WebLogic Kubernetes Operator refer to Version 23.1.1

Recent changes and known issues

See the Release Notes for recent changes and known issues for Oracle Access Management domain deployment on Kubernetes.


See here for limitations in this release.

Getting started

This documentation explains how to configure OAM on a Kubernetes cluster where no other Oracle Identity Management products will be deployed. For detailed information about this type of deployment , start at Prerequisites and follow this documentation sequentially.

If performing an Enterprise Deployment where multiple Oracle Identity Management products are deployed, refer to the Enterprise Deployment Guide for Oracle Identity and Access Management in a Kubernetes Cluster instead.

Documentation for earlier releases

To view documentation for an earlier release, see: