Oracle Identity Governance

The WebLogic Kubernetes Operator supports deployment of Oracle Identity Governance (OIG).

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

The operator has several key features to assist you with deploying and managing OIG domains in a Kubernetes environment. You can:

  • Create OIG 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 OIG Services for external access.
  • Scale OIG 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 OIG instance using Prometheus and Grafana.

Current production release

The current production release for the Oracle Identity Governance domain deployment on Kubernetes is 22.4.1. This release uses the WebLogic Kubernetes Operator version 3.4.2.

For 3.3.X WebLogic Kubernetes Operator refer to Version 22.3.1

Recent changes and known issues

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

Limitations

See here for limitations in this release.

Getting started

This documentation explains how to configure OIG 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, 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: