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: documentation/staging/content/release-notes.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -146,9 +146,9 @@ Updated several dependencies, including the Oracle Linux base for the container
146
146
##### Features
147
147
148
148
* The operator's container image is based on Oracle Linux 8.
149
-
* WebLogic Server container images based on Oracle Linux 8 are supported.
149
+
* WebLogic Server container images based on Oracle Linux 8 are supported.
150
150
*[Online updates]({{<relref "/userguide/managing-domains/model-in-image/runtime-updates/_index.md#online-updates">}}) of dynamic configuration changes for Model in Image.
151
-
* Automatic injection of the [WebLogic Monitoring Exporter](https://github.com/oracle/weblogic-monitoring-exporter) as a sidecar container.
151
+
* Automatic injection of the [WebLogic Monitoring Exporter](https://github.com/oracle/weblogic-monitoring-exporter) as a sidecar container.
152
152
*[Events]({{< relref "/userguide/managing-domains/domain-events.md" >}}) are generated at important moments in the life cycle of the operator or a domain.
153
153
*[PodDisruptionBudgets]({{<relref "/userguide/managing-domains/domain-lifecycle/startup.md#draining-a-node-and-poddisruptionbudget">}}) are generated for clusters improving the ability to maintain cluster availability during planned node shutdowns and Kubernetes upgrade.
154
154
* Additional scripts to assist with common tasks, such as the `scaleCluster.sh` script.
Clone the [WebLogic Kubernetes Operator repository](https://github.com/oracle/weblogic-kubernetes-operator) to your machine. We will use several scripts in this repository to create a WebLogic domain. This sample was tested with v3.1.1, but should work with the latest release.
29
+
Clone the [WebLogic Kubernetes Operator repository](https://github.com/oracle/weblogic-kubernetes-operator) to your machine. You will use several scripts in this repository to create a WebLogic domain. This sample was tested with v3.3.7, but should work with the latest release.
Now that we have created the AKS cluster, installed the operator, and verified that the operator is ready to go, we can have the operator create a WLS domain.
88
+
Now that You have created the AKS cluster, installed the operator, and verified that the operator is ready to go, you can have the operator create a WLS domain.
91
89
92
90
##### Create secrets
93
91
94
-
We will use the `kubernetes/samples/scripts/create-weblogic-domain-credentials/create-weblogic-credentials.sh` script to create the domain credentials as a Kubernetes secret. Please run:
92
+
You will use the `kubernetes/samples/scripts/create-weblogic-domain-credentials/create-weblogic-credentials.sh` script to create the domain credentials as a Kubernetes secret. Please run:
95
93
96
94
```
97
95
# cd kubernetes/samples/scripts/create-weblogic-domain-credentials
@@ -104,8 +102,7 @@ secret/domain1-weblogic-credentials created
104
102
secret/domain1-weblogic-credentials labeled
105
103
The secret domain1-weblogic-credentials has been successfully created in the default namespace.
106
104
```
107
-
108
-
We will use the `kubernetes/samples/scripts/create-kubernetes-secrets/create-docker-credentials-secret.sh` script to create the Docker credentials as a Kubernetes secret. Please run:
105
+
You will use the `kubernetes/samples/scripts/create-kubernetes-secrets/create-docker-credentials-secret.sh` script to create the Docker credentials as a Kubernetes secret. Please run:
109
106
110
107
```shell
111
108
# Please change imagePullSecretNameSuffix if you change pre-defined value "regcred" before generating the configuration files.
**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.
143
139
144
140
##### Create WebLogic Domain
145
-
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.
141
+
You 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 you created previously.
146
142
147
143
{{% notice note %}} The `create-domain.sh` script and its inputs file are for demonstration purposes _only_; its contents and the domain resource file that it generates for you might change without notice. In production, we strongly recommend that you use the WebLogic Image Tool and WebLogic Deploy Tooling (when applicable), and directly work with domain resource files instead.
148
144
{{% /notice%}}
149
145
150
-
We need to set up the domain configuration for the WebLogic domain.
146
+
You need to set up the domain configuration for the WebLogic domain.
151
147
152
148
1. Check if resources are ready.
153
149
@@ -166,10 +162,8 @@ We need to set up the domain configuration for the WebLogic domain.
You will see output with `PASS` if all the resources are ready. The following is an example of output:
@@ -181,10 +175,8 @@ We need to set up the domain configuration for the WebLogic domain.
181
175
Azure Kubenetes Service instacne: wlsaks1612795811
182
176
Azure storage account: wlsstorage1612795811
183
177
Azure file share: wls-weblogic-1612795811
184
-
Kubenetes secret for Azure storage: wlsazure-secret
185
178
Kubenetes secret for Docker Account: regcred
186
179
Kubenetes secret for Weblogic domain: domain1-weblogic-credentials
187
-
Persistent Volume: wls-azurefile-1612795811
188
180
Persistent Volume Claim: wls-azurefile-1612795811
189
181
```
190
182
@@ -301,7 +293,7 @@ We need to set up the domain configuration for the WebLogic domain.
301
293
troubleshoot the reason and resolve it before proceeding to the next
302
294
step.
303
295
304
-
{{% notice note %}} This sample creates WebLogic Server pods with reasonable values for memory, CPU, and JVM heap size (as a percentage of memory). You can supply different values. Edit `~/azure/weblogic-on-aks/domain1.yaml` and set the desired values for `serverPodMemoryRequest`, `serverPodMemoryLimit`, `serverPodCpuRequest`, `serverPodCpuLimit` and `javaOptions` before running `./create-domain.sh -i ~/azure/weblogic-on-aks/domain1.yaml -o ~/azure -e -v`.
296
+
{{% notice note %}} This sample creates WebLogic Server pods with reasonable values for memory, CPU, and JVM heap size (as a percentage of memory). These settings were determined by running a skeleton WebLogic domain with minimal or no deployed services and applications on potentially limited or heavily shared container environments. For advice about tuning CPU and memory requests and limits for broader use cases or in a production environment, see the [Pod memory and CPU resources](https://oracle.github.io/weblogic-kubernetes-operator/faq/resource-settings/) FAQ. You can supply different values. Edit `~/azure/weblogic-on-aks/domain1.yaml` and set the desired values for `serverPodMemoryRequest`, `serverPodMemoryLimit`, `serverPodCpuRequest`, `serverPodCpuLimit` and `javaOptions` before running `./create-domain.sh -i ~/azure/weblogic-on-aks/domain1.yaml -o ~/azure -e -v`.
305
297
{{% /notice%}}
306
298
307
299
Here is an excerpt showing reasonable values:
@@ -344,7 +336,7 @@ We need to set up the domain configuration for the WebLogic domain.
344
336
type: LoadBalancer
345
337
```
346
338
347
-
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.
339
+
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 your domain values.
348
340
349
341
```yaml
350
342
apiVersion: v1
@@ -510,7 +502,7 @@ For input values, you can edit `kubernetes/samples/scripts/create-weblogic-domai
510
502
| `dockerEmail` | `yourDockerEmail` | Oracle Single Sign-On (SSO) account email, used to pull the WebLogic Server Docker image. |
511
503
| `dockerPassword` | `yourDockerPassword`| Password for Oracle SSO account, used to pull the WebLogic Server Docker image, in clear text. |
512
504
| `dockerUserName` | `yourDockerId` | The same value as `dockerEmail`. |
513
-
| `namePrefix` | `0730` | Alphanumeric value used as a disambiguation prefix for several Kubernetes resources. |
505
+
| `namePrefix` | `wls` | Alphanumeric value used as a disambiguation prefix for several Kubernetes resources. |
514
506
515
507
If you don't want to change the other parameters, you can use the default values. Please make sure no extra whitespaces are added!
The script will print the Administration Server address after a successful deployment. The default user name for the Administration Console is `weblogic` and the default password is `welcome1`. Please change this for production deployments. To interact with the cluster using `kubectl`, use `az aks get-credentials` as shown in the script output.
530
522
531
-
{{% notice info %}} You now have created an AKS cluster with `PersistentVolumeClaim` and `PersistentVolume` to contain the WLS domain configuration files. Using those artifacts, you have used the operator to create a WLS domain.
523
+
{{% notice info %}} You now have created an AKS cluster with Azure Files NFS share to contain the WLS domain configuration files. Using those artifacts, you have used the operator to create a WLS domain.
532
524
{{% /notice %}}
533
525
534
526
#### Deploy sample application
@@ -574,22 +566,27 @@ In the example, the application address is: `http://52.224.248.40:8001/testwebap
574
566
575
567
The test application will list the server host and server IP on the page.
576
568
577
-
#### Access WebLogic Server logs
569
+
#### Validate NFS volume
578
570
579
-
The logs are stored in the Azure file share. Follow these steps to access the log:
571
+
There are several approaches to validate the NFS volume:
580
572
581
-
1. Go to the [Azure Portal](https://ms.portal.azure.com).
582
-
2. Go to your resource group.
583
-
3. Open the storage account.
584
-
4. In the "File service" section of the left panel, select File shares.
585
-
5. Select the file share name (e.g. weblogic in this example).
586
-
6. Select logs.
587
-
7. Select domain1.
588
-
8. WebLogic Server logs are listed in the folder.
573
+
- Use Azure Storage browser. Make sure you have permission to access the NFS server, see [Azure Storage firewalls and virtual networks document](https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal)
574
+
- Mount the same NFS share in an existing virtual machine from Azure. Access files from the mounted path, see [Mount Azure NFS file share to Linux](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-how-to-mount-nfs-shares).
589
575
590
-
{{%expand "Click here to view the WebLogic Server logs screenshot." %}}
591
-
592
-
{{% /expand %}}
576
+
Use `kubectl exec` to enter the admin server pod to check file system status:
577
+
578
+
```shell
579
+
kubectl exec -it domain1-admin-server -- df -h
580
+
```
581
+
582
+
You will find output like the following, with filesystem `${AKS_PERS_STORAGE_ACCOUNT_NAME}.file.core.windows.net:/${AKS_PERS_STORAGE_ACCOUNT_NAME}/${AKS_PERS_SHARE_NAME}`, size `100G`, and mounted on `/shared`:
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 manage and maintain only the agent nodes. As a managed Kubernetes service, AKS is free - you pay for only the agent nodes within your clusters, not for the masters.
1
+
Azure Kubernetes Service (AKS) 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 manage and maintain only the agent nodes. As a managed Kubernetes service, AKS is free - you pay for only the agent nodes within your clusters, not for the masters.
2
2
3
-
To learn more, see [What is Azure Kubernetes Service?](https://docs.microsoft.com/en-us/azure/aks/intro-kubernetes)
3
+
To learn more, see [What is Azure Kubernetes Service?](https://docs.microsoft.com/azure/aks/intro-kubernetes)
0 commit comments