You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-source/content/samples/simple/azure-kubernetes-service/_index.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -18,28 +18,28 @@ description: "Sample for using the operator to set up a WLS cluster on the Azure
18
18
19
19
### Introduction
20
20
21
-
This sample demonstrates how to use the [Oracle WebLogic Server Kubernetes Operator]({{< relref "/_index.md" >}}) (hereafter "the operator") to set up a WebLogic Server (WLS) cluster on the Azure Kubernetes Service (AKS). After going through the steps, your WLS domain runs on an AKS cluster. You have several options for managing the cluster, depending on which [domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}) you choose. With Domain in PV, you can manage your WLS domain by accessing the WebLogic Server Administration Console or WLST. With Model in Image you use the operator to perform WLS administrative operations.
21
+
This sample demonstrates how to use the [Oracle WebLogic Server Kubernetes Operator]({{< relref "/_index.md" >}}) (hereafter "the operator") to set up a WebLogic Server (WLS) cluster on the Azure Kubernetes Service (AKS). After going through the steps, your WLS domain runs on an AKS cluster. You have several options for managing the cluster, depending on which [domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}) you choose. With Domain in PV, you can manage your WLS domain by accessing the WebLogic Server Administration Console or WLST. With Model in Image, you use the operator to perform WLS administrative operations.
22
22
23
23
#### Azure Kubernetes Service cluster
24
24
25
25
Azure Kubernetes Service makes it simple to deploy a managed Kubernetes cluster in Azure. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. As a hosted Kubernetes service, Azure handles critical tasks like health monitoring and maintenance for you. The Kubernetes masters are managed by Azure. You only manage and maintain the agent nodes. As a managed Kubernetes service, AKS is free - you only pay for the agent nodes within your clusters, not for the masters.
26
26
27
-
To learn more, please see the [What is Azure Kubernetes Service?](https://docs.microsoft.com/en-us/azure/aks/intro-kubernetes).
27
+
To learn more, see the [What is Azure Kubernetes Service?](https://docs.microsoft.com/en-us/azure/aks/intro-kubernetes).
28
28
29
29
#### Domain home source types
30
30
31
-
This sample demonstrates running the WebLogic cluster on AKS using two domain home types. The instructions for each are selfcontained and independent. This section lists the domain home source types recommended for use with AKS, along with some benefits of each. For complete details on domain home source types, see [Choose a domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}).
31
+
This sample demonstrates running the WebLogic cluster on AKS using two domain home types. The instructions for each are self-contained and independent. This section lists the domain home source types recommended for use with AKS, along with some benefits of each. For complete details on domain home source types, see [Choose a domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}).
32
32
33
-
-[Model in Image]({{< relref "/samples/simple/azure-kubernetes-service/model-in-image.md" >}}): running the WebLogic cluster on AKS with domain home in image offers the following benefits.
33
+
-[Model in Image]({{< relref "/samples/simple/azure-kubernetes-service/model-in-image.md" >}}): running the WebLogic cluster on AKS with domain home in image offers the following benefits:
34
34
35
35
- Reuse image to create different domains with different `domainUID` and different configurations.
36
36
- Mutate the domain home configuration with additional model files supplied in a `ConfigMap`. Many such changes do not need to restart the entire domain for the change to take effect.
37
37
- The model file syntax is far simpler and less error prone than the configuration override syntax, and, unlike configuration overrides, allows you to directly add data sources and JMS modules.
38
38
39
-
-[Domain in PV]({{< relref "/samples/simple/azure-kubernetes-service/domain-on-pv.md" >}}): running the WebLogic cluster on AKS with domain home in PV offers the following benefits.
39
+
-[Domain in PV]({{< relref "/samples/simple/azure-kubernetes-service/domain-on-pv.md" >}}): running the WebLogic cluster on AKS with domain home in PV offers the following benefits:
40
40
41
41
- Use standard Oracle-provided images with patches installed.
42
-
- No docker environment required. You are able to run your business quickly without building knowledge of docker.
42
+
- No Docker environment required. You are able to run your business quickly without building knowledge of Docker.
43
43
- Mutate the live domain configuration with Administration Console from a browser or WLST.
>**Note**: If you run into VM size failure, see [Troubleshooting - Virtual Machine size is not supported]({{< relref "/samples/simple/azure-kubernetes-service/troubleshooting#virtual-machine-size-is-not-supported" >}}).
40
+
**Note**: If you run into VM size failure, see [Troubleshooting - Virtual Machine size is not supported]({{< relref "/samples/simple/azure-kubernetes-service/troubleshooting#virtual-machine-size-is-not-supported" >}}).
> **Note**: If the `NAME` column in your output is missing any of the values shown above, please reexamine your execution of the preceding steps in this sample to ensure that you correctly followed all of them. The `default-token-mwdj8` shown above will have a different ending in your output.
124
+
**Note**: If the `NAME` column in your output is missing any of the values shown above, please reexamine your execution of the preceding steps in this sample to ensure that you correctly followed all of them. The `default-token-mwdj8` shown above will have a different ending in your output.
125
125
126
126
##### Create WebLogic Domain
127
127
We will use the `kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain.sh` script to create the WLS domain in the persistent volume we created previously.
128
128
129
129
We need to set up the domain configuration for the WebLogic domain.
130
130
131
-
1. Check if resources are ready
131
+
1. Check if resources are ready.
132
132
133
133
If you used the automation script to create the AKS cluster, skip this step and go to step 2.
134
134
135
-
If you create Azure resources step by step according to the steps above, validate all the resources created above using the script `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/validate.sh`.
135
+
If you created Azure resources, step-by-step, according to the previous steps, then validate that all the resources above were created by using the script `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/validate.sh`.
136
136
137
137
Use the following commands to check if the resources are ready:
138
138
@@ -165,7 +165,7 @@ We need to set up the domain configuration for the WebLogic domain.
165
165
Persistent Volume Claim: wls-azurefile-1612795811
166
166
```
167
167
168
-
2. Now let's ask the operator to create a WebLogic Server domain within the AKS cluster.
168
+
2. Now let's ask the operator to create a WebLogic Server domain within the AKS cluster.
169
169
170
170
For complete details on domain creation, see [Domain home on a PV - Use the script to create a domain]({{< relref "/samples/simple/domains/domain-home-on-pv#use-the-script-to-create-a-domain" >}}). If you do not want the complete details and just want to continue with the domain creation for AKS, invoke the `create-domain.sh` script as shown next.
171
171
@@ -191,11 +191,11 @@ We need to set up the domain configuration for the WebLogic domain.
191
191
Failed to pull image "container-registry.oracle.com/middleware/weblogic:12.2.1.4": rpc error: code = Unknown desc = Error response from daemon: Get https://container-registry-phx.oracle.com/v2/middleware/weblogic/manifests/12.2.1.4: unauthorized: authentication required
192
192
```
193
193
194
-
Ensure the arguments you passed to the script `create-docker-credentials-secret.sh` are correct with respect to your Oracle SSO credentials.
194
+
Ensure that the arguments you passed to the script `create-docker-credentials-secret.sh` are correct with respect to your Oracle SSO credentials.
195
195
196
196
The following example output shows the WebLogic domain was created successfully.
197
197
198
-
{{%expand "Click here to view the example output." %}}
198
+
{{%expand "Click here to view the example output." %}}
@@ -270,7 +270,7 @@ We need to set up the domain configuration for the WebLogic domain.
270
270
```
271
271
{{% /expand %}}
272
272
273
-
>**Note**: If your output does not show a successful completion, you must
273
+
**Note**: If your output does not show a successful completion, you must
274
274
troubleshoot the reason and resolve it before proceeding to the next
275
275
step.
276
276
@@ -297,7 +297,7 @@ We need to set up the domain configuration for the WebLogic domain.
297
297
type: LoadBalancer
298
298
```
299
299
300
-
Use the sample configuration file `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/domain-on-pv/cluster-lb.yaml` to create a load balancer service for the managed servers. If you are choosing not to use the predefined YAML file and instead created new one with customized values, then substitute the following content with you domain values.
300
+
Use the sample configuration file `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/domain-on-pv/cluster-lb.yaml` to create a load balancer service for the Managed Servers. If you are choosing not to use the predefined YAML file and instead created new one with customized values, then substitute the following content with you domain values.
301
301
302
302
```yaml
303
303
apiVersion: v1
@@ -356,7 +356,7 @@ We need to set up the domain configuration for the WebLogic domain.
{{% notice tip %}} If Kubernetes advertises the WebLogic pod as `Running` you can be assured the WebLogic Server actually is running because the operator ensures the Kubernetes health checks are actually polling the WebLogic health check mechanism.
359
+
{{% notice tip %}} If Kubernetes advertises the WebLogic pod as `Running` you can be assured the WebLogic Server actually is running because the operator ensures that the Kubernetes health checks are actually polling the WebLogic health check mechanism.
360
360
{{% /notice %}}
361
361
362
362
Get the addresses of the Administration Server and Managed Servers (please waitfor the external IP addresses to be assigned):
@@ -439,7 +439,7 @@ To deploy a sample application on WLS, you may skip to the section [Deploy sampl
439
439
440
440
If you want to automate the above steps of creating AKS cluster and WLS domain, you can use the script `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/create-domain-on-aks.sh`.
441
441
442
-
The sample script will create a WLS domain home on the AKS cluster, including
442
+
The sample script will create a WLS domain home on the AKS cluster, including:
443
443
- Creating a new Azure resource group, with a new Azure Storage Account and Azure File Share to allow WebLogic to persist its configuration and data separately from the Kubernetes pods that run WLS workloads.
444
444
- Creating WLS domain home.
445
445
- Generating the domain resource YAML files, which can be used to restart the Kubernetes artifacts of the corresponding domain.
@@ -452,7 +452,7 @@ For input values, you can edit `kubernetes/samples/scripts/create-weblogic-domai
452
452
|`azureServicePrincipalClientSecret`|`8693089o-q190-45ps-9319-or36252s3s90`| A client secret of your service principal; refer to the client secret in the [Create Service Principal]({{< relref "/samples/simple/azure-kubernetes-service/domain-on-pv#create-a-service-principal-for-aks">}}) section. |
453
453
|`azureServicePrincipalTenantId`|`72s988os-86s1-cafe-babe-2q7pq011qo47`| Tenant (Directory ) ID of your service principal; refer to the client secret in the [Create Service Principal]({{< relref "/samples/simple/azure-kubernetes-service/domain-on-pv#create-a-service-principal-for-aks">}}) section. |
454
454
|`dockerEmail`|`yourDockerEmail`| Oracle Single Sign-On (SSO) account email, used to pull the WebLogic Server Docker image. |
455
-
|`dockerPassword`|`yourDockerPassword`| Password for Oracle SSO account, used to pull the WebLogic Server Docker image. In clear text. |
455
+
|`dockerPassword`|`yourDockerPassword`| Password forOracle SSO account, used to pull the WebLogic Server Docker image,in clear text. |
456
456
|`dockerUserName`|`yourDockerId`| The same value as `dockerEmail`. |
457
457
|`namePrefix`|`0730`| Alphanumeric value used as a disambiguation prefix for several Kubernetes resources. |
Copy file name to clipboardExpand all lines: docs-source/content/samples/simple/azure-kubernetes-service/includes/create-aks-cluster-body-01.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Found an existing application instance of "5pn2s201-nq4q-43n1-z942-p9r9571qr3rp"
32
32
Insufficient privileges to complete the operation.
33
33
```
34
34
35
-
The problem may be a pre-existing service principal with the same name. Either delete the other Service Principal or pick a different name.
35
+
The problem may be a pre-existing service principal with the same name. Either delete the other service principal or pick a different name.
36
36
37
37
Successful output will look like the following:
38
38
@@ -74,9 +74,9 @@ You will need an Oracle account. The following steps will direct you to accept t
74
74
75
75
- In a web browser, navigate to https://container-registry.oracle.com and log in using the Oracle Single Sign-On authentication service. If you do not already have SSO credentials, at the top of the page, click the **Sign In** link to create them.
76
76
- The Oracle Container Registry provides a WebLogic Server 12.2.1.4.0 Docker image, which already has the necessary patches applied, and the Oracle WebLogic Server 12.2.1.4.0 and 14.1.1.0.0 images, which do not require any patches.
77
-
- Ensure Docker desktop is running. Find and then pull the WebLogic 12.2.1.4 install image:
77
+
- Ensure that Docker desktop is running. Find and then pull the WebLogic 12.2.1.4 install image:
If you have problems accessing the Oracle Container Registry, you can build your own docker images from the [Oracle GitHub repository](https://github.com/oracle/docker-images/tree/main/OracleWebLogic/dockerfiles).
82
+
If you have problems accessing the Oracle Container Registry, you can build your own Docker images from the [Oracle GitHub repository](https://github.com/oracle/docker-images/tree/main/OracleWebLogic/dockerfiles).
Copy file name to clipboardExpand all lines: docs-source/content/samples/simple/azure-kubernetes-service/includes/create-aks-cluster-body-02.txt
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
#### Create the AKS cluster
2
2
3
-
This sample requires that you disable the AKS addon `http_application_routing` by default. If you want to enable `http_application_routing`, please follow [HTTP application routing](https://docs.microsoft.com/azure/aks/http-application-routing).
3
+
This sample requires that you disable the AKS addon `http_application_routing` by default. If you want to enable `http_application_routing`, then follow [HTTP application routing](https://docs.microsoft.com/azure/aks/http-application-routing).
4
4
5
5
Run the following commands to create the AKS cluster instance.
6
6
@@ -43,12 +43,11 @@ Successful output will look similar to:
43
43
Merged "wlsaks1596087429" as current context in /home/username/.kube/config
44
44
```
45
45
46
-
After your Kubernetes cluster is up and running, run the following commands to make sure kubectl can access the Kubernetes cluster:
46
+
After your Kubernetes cluster is up and running, run the following commands to make sure `kubectl` can access the Kubernetes cluster:
47
47
48
48
```shell
49
49
$ kubectl get nodes -o wide
50
50
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
0 commit comments