Installing the WebLogic Kubernetes Operator Add-on
On Compute Cloud@Customer, You can enable the WebLogic Kubernetes Operator add-on when you create a cluster or for an existing cluster.
To bring the WebLogic Server to the running state, create additional rules in separate WebLogic Server security lists for the control plane and worker subnets, and for the pod subnet if you're using VCN-Native Pod Networking. See Ports Required by WebLogic Server.
Add-on installation remains in Accepted state and waits until the cluster is in the Active state.
After the cluster is in the Active state, the WebLogic Kubernetes Operator is in Needs Attention state until a node pool is created for the cluster.
When a node-pool has been created for the cluster, the add-on is reconciled, and the add-on is in Ready state unless some other problem exists. See Add-on Reconciliation.
Enabling the WebLogic Kubernetes Operator add-on on a VCN-Native Pod Networking cluster requires an entry for 169.254.169.254 in crio-noproxy node metadata for the nodepools where the add-on pods might be scheduled. See "Proxy settings" in the CLI procedure in Creating an OKE Worker Node Pool.
See the following sections: