Deploy the Domain

To inform the operator of a new WebLogic or FMW domain, you must create an operator Domain resource object in Kubernetes. Starting in WKO 4.0.0, the operator also needs an operator Cluster resource object for every cluster in the domain. This separation is required to work with the Kubernetes Horizontal Pod Autoscaler (HPA) to allow it to automatically scale clusters based on load (but only up to the maximum size of the WebLogic cluster). For more information, see this WebLogic Kubernetes Operator Scaling documentation.

WKT UI generated the required operator resource objects for your domain because of the project settings. Go to the Kubernetes > WebLogic Domain page. Before continuing, there are a few things to understand:

1. We are using the Oracle Container Registry (OCR) to pull the primary image. You must log in and create an Auth Token that will be used by Docker and Kubernetes instead of your password. See the following image to understand how to do that. You will need to copy this Auth Token value since it will be needed when creating the Image Registry Credentials entry that will be used to create a Kubernetes pull secret for the primary image.
2. For your user to be allowed to pull images, you must accept the Terms and Conditions for that repository. Note that only authorized users on your company’s Support CSID will be allowed to pull from the weblogic_cpu repository.
3. For real world usage, Oracle strongly recommended using fully patched images; for example, from the weblogic_cpu registry. For the purposes of this guide, it is acceptable to use the public weblogic repository if you do not have permission to access the weblogic_cpu repository.
4. Make sure to choose an image for the version of WebLogic Server that you want to use. For example, at the time of writing, the 15.1.1.0-generic-jdk17-ol9-251002 image is the newest one available in the weblogic repository. We chose to use the “Dated Tag” so that it is obvious what image we are using. For this image, the Primary Image Tag value would be container-registry.oracle.com/middleware/weblogic:15.1.1.0-generic-jdk17-ol9-251002.

Fill in the form fields, as described in the following table.

After you filled out the fields in the preceding table, you need to look at some additional fields contained in tables, shown in the following image.

1. First, look at the Clusters table. As you can see, the cluster from your model has been added to this table (by the earlier invocation of the Prepare Model action). If you do not see the cluster, run Prepare Model again to populate the table.
2. Notice that the Replicas value for the cluster is set to the maximum size of the cluster, as specified in the model. Select the Pencil icon toward the right end of the row. Notice that you cannot set the Replicas value higher than 10. After you are done, change the value to 2 and click OK.
3. Next, look at the Model Variables Overrides section. This section lets you override the values specified in the variables model file in the auxiliary image using a Kubernetes ConfigMap. Because you do not need to override these values, you can move on to the Secrets section.

The Secrets section contains all model-defined secrets and lets you specify the user name and password. In the preceding image, notice that the secret associated with your MySQL database connection is already populated with the proper image name. This value was removed from the model (or the variable reference) by the Prepare Model action and added here. If you run Prepare Model more than once, you will lose this value and must enter it manually. WDT generally will not populate password values, so you need to enter your MySQL database password you provided when you ran Quick Start scripts/wkoDeployMySQL script.

Before you deploy the domain, you must deploy the MySQL database. You will deploy the database to the same namespace as the domain, so you need to create the following Kubernetes objects to deploy the database:

• todolist-domain-ns Namespace – The Kubernetes namespace where both the WebLogic or FMW domain and MySQL database will reside.
• ocr Secret – The Kubernetes image pull secret for pulling images from the Oracle Container Registry.
• mysql Secret – The Kubernetes secret that holds the root password, user name, and password of the user the ToDo List application uses to connect to the database.
• todolist-mysql-cm ConfigMap – The Kubernetes ConfigMap used to hold the init-schema.sql script to initialize the MySQL database on startup.
• todolist-mysql-deployment Deployment – The Kubernetes deployment that will start and manage the MySQL database.
• mysql Service – The Kubernetes service that exposes the MySQL database by the mysql DNS name to the WebLogic managed servers.

To make this easier, go to the QuickStart directory and do the following:

1. Edit the demarcated section of the setQuickstartEnv shell script to match your environment.
2. Source (macOS or Linux) or run the setQuickstartEnv shell script.
3. Change to the scripts subdirectory and run the wkoDeployMySQL script, which creates the Kubernetes objects described previously to start the MySQL database.

Now that the MySQL database is running at the hostname mysql (inside the namespace), click Deploy Domain. This action takes some time to run. Even after the action finishes, you need to wait a few minutes for the operator to introspect the domain and start the servers. Use Get Domain Status to verify that the domain is up, and all servers are running, as shown in the following image.

After your domain is ready, move onto the next section.