This section provides answers to frequently asked questions.
Answers to commonly asked newcomer questions.
Considerations for managing namespaces while the operator is running.
My domain will not start and I see errors like `ImagePullBackoff` or `Cannot pull image`.
One or more WebLogic Server instances in my domain will not start and I see errors in the server log like this: Boot identity not valid.
One or more WebLogic Server instances in my domain will not start and the domain resource `status` or the pod log reports errors like this: Domain secret mismatch.
The operator creates a Pod for each WebLogic Server instance that is started. The Kubernetes Scheduler then selects a Node for each Pod. Because the default scheduling algorithm gives substantial weight to selecting a Node where the necessary container images have already been pulled, this often results in Kubernetes running many of the Pods for WebLogic Server instances on the same Node while other Nodes are not fairly utilized. This is commonly known as the Node heating problem.
To support Fast Application Notifications (FAN), Oracle databases configure GRID (Oracle Grid Infrastructure). GRID is typically associated with (and required by) Oracle RAC databases but can also be used in other configurations. Oracle Autonomous Database-Serverless (ATP-S) does not provide GRID.
If you are running your Kubernetes cluster on Oracle Container Engine for Kubernetes (OKE), and you use OCI File Storage (FSS) for persistent volumes to store the WebLogic domain home, then the file system handling, as demonstrated in the operator persistent volume sample, will require an update to properly initialize the file ownership on the persistent volume when the domain is initially created.
If you are running your Kubernetes cluster on Oracle Container Engine for Kubernetes (OKE), then you can have OCI automatically provision load balancers for you by creating a `Service` of type `LoadBalancer` instead of (or in addition to) installing an ingress controller like Traefik or Voyager.
I need to provide an instance with access to a PersistentVolumeClaim.
I need to provide an instance with access to a ConfigMap.
This FAQ describes approaches for giving WebLogic applications access to WebLogic JMS or EJB resources when either the applications or their resources are located in Kubernetes. This includes between different Kubernetes namespaces within the same Kubernetes cluster, between different Kubernetes clusters, and between a non-Kubernetes location and Kubernetes.
If you are running Coherence on Kubernetes, either inside a WebLogic domain or standalone, then there are some additional requirements to make sure that Coherence can form clusters.
Tune container memory and CPU usage by configuring Kubernetes resource requests and limits, and tune a WebLogic JVM heap usage using the `USER_MEM_ARGS` environment variable in your Domain YAML file.
Why am I seeing these security warnings?