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:
The current production release for the Oracle Access Management domain deployment on Kubernetes is 22.2.1. This release uses the WebLogic Kubernetes Operator version 3.3.0.
This release of the documentation can also be used for 3.1.X and 3.2.0 WebLogic Kubernetes Operator. For 3.0.X WebLogic Kubernetes Operator refer to Version 21.4.1
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.
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.
To view documentation for an earlier release, see: