Skip to content

fix x-refs #2052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 13, 2020
Merged

fix x-refs #2052

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs-source/content/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@ draft: false
#### Operator 3.1.0

* All fixes included in 3.0.1, 3.0.2, and 3.0.3 are included in 3.1.0.
* Sample [scripts to start and stop server instances](userguide/managing-domains/domain-lifecycle/startup.md#domain-lifecycle-sample-scripts) ([#2002](https://github.com/oracle/weblogic-kubernetes-operator/pull/2002)).
* Support running with [OpenShift restrictive SCC](security/openshift.md) ([#2007](https://github.com/oracle/weblogic-kubernetes-operator/pull/2007)).
* Updated [default resource and Java options](faq/resource-settings.md) ([#1775](https://github.com/oracle/weblogic-kubernetes-operator/pull/1775)).
* Sample [scripts to start and stop server instances]({{< relref "/userguide/managing-domains/domain-lifecycle/startup#domain-lifecycle-sample-scripts" >}}) ([#2002](https://github.com/oracle/weblogic-kubernetes-operator/pull/2002)).
* Support running with [OpenShift restrictive SCC]({{< relref "/security/openshift#create-a-custom-security-context-constraint" >}}) ([#2007](https://github.com/oracle/weblogic-kubernetes-operator/pull/2007)).
* Updated [default resource and Java options]({{< relref "/faq/resource-settings.md" >}}) ([#1775](https://github.com/oracle/weblogic-kubernetes-operator/pull/1775)).
* Introspection failures are logged to the operator's log ([#1787](https://github.com/oracle/weblogic-kubernetes-operator/pull/1787)).
* Mirror introspector log to a rotating file in the log home ([#1827](https://github.com/oracle/weblogic-kubernetes-operator/pull/1827)).
* Reflect introspector status to domain status ([#1832](https://github.com/oracle/weblogic-kubernetes-operator/pull/1832)).
* Ensure operator detects pod state changes even when watch events are not delivered ([#1811](https://github.com/oracle/weblogic-kubernetes-operator/pull/1811)).
* Support configurable WDT model home ([#1828](https://github.com/oracle/weblogic-kubernetes-operator/pull/1828)).
* [Namespace management enhancements](faq/namespace-management.md) ([#1860](https://github.com/oracle/weblogic-kubernetes-operator/pull/1860)).
* [Namespace management enhancements]({{< relref "/faq/namespace-management.md" >}}) ([#1860](https://github.com/oracle/weblogic-kubernetes-operator/pull/1860)).
* Limit concurrent pod shut down while scaling down a cluster ([#1892](https://github.com/oracle/weblogic-kubernetes-operator/pull/1892)).
* List continuation and watch bookmark support ([#1881](https://github.com/oracle/weblogic-kubernetes-operator/pull/1881)).
* Fix scaling script when used with dedicated namespace mode ([#1921](https://github.com/oracle/weblogic-kubernetes-operator/pull/1921)).
Expand Down
34 changes: 17 additions & 17 deletions docs-source/content/samples/simple/azure-kubernetes-service/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,9 +109,9 @@ You will need an Oracle account. The following steps will direct you to accept t
1. Obtain the WebLogic Server image from the [Oracle Container Registry](https://container-registry.oracle.com/).

a. First time users, [follow these directions](/weblogic-kubernetes-operator/userguide/managing-domains/domain-in-image/base-images/#obtaining-standard-images-from-the-oracle-container-registry).

b. Find and then pull the WebLogic 12.2.1.3 install image:

```bash
$ docker pull container-registry.oracle.com/middleware/weblogic:12.2.1.3
```
Expand All @@ -125,7 +125,7 @@ $ git clone https://github.com/oracle/weblogic-kubernetes-operator.git
#cd weblogic-kubernetes-operator
$ git checkout v3.0.3
```

{{% notice info %}} The following sections of the sample instructions will guide you, step-by-step, through the process of setting up a WebLogic cluster on AKS - remaining as close as possible to a native Kubernetes experience. This lets you understand and customize each step. If you wish to have a more automated experience that abstracts some lower level details, you can skip to the [Automation](#automation) section.
{{% /notice %}}

Expand Down Expand Up @@ -389,13 +389,13 @@ Kubernetes Operators use [Helm](https://helm.sh/) to manage Kubernetes applicati
```bash
$ helm repo add weblogic-operator https://oracle.github.io/weblogic-kubernetes-operator/charts
$ helm repo update
$ helm install weblogic-operator weblogic-operator/weblogic-operator --version "3.0.0"
$ helm install weblogic-operator weblogic-operator/weblogic-operator --version "3.0.3"
```

The output will show something similar to the following:

```bash
$ helm install weblogic-operator weblogic-operator/weblogic-operator --version "3.0.0"
$ helm install weblogic-operator weblogic-operator/weblogic-operator --version "3.0.3"
NAME: weblogic-operator
LAST DEPLOYED: Wed Jul 1 23:47:44 2020
NAMESPACE: default
Expand Down Expand Up @@ -485,7 +485,7 @@ Now that we have created the AKS cluster, installed the operator, and verified t
We need to set up the domain configuration for the WebLogic domain. This step uses the configuration generated previously.

Validate all the resources created above using the script `kubernetes/samples/scripts/create-weblogic-domain-on-azure-kubernetes-service/validate.sh`.

Use the following commands to check if the resources are ready:

```bash
Expand Down Expand Up @@ -534,13 +534,13 @@ Now that we have created the AKS cluster, installed the operator, and verified t
status on iteration 2 of 20
pod domain1-create-weblogic-sample-domain-job-4l767 status is Running
```

If you see error messages that include the status `ImagePullBackOff` along with output similar to the following, it is likely your credentials for the Oracle Container Registry have not been successfully conveyed to the AKS cluster.

```bash
Failed to pull image "container-registry.oracle.com/middleware/weblogic:12.2.1.3": rpc error: code = Unknown desc = Error response from daemon: Get https://container-registry-phx.oracle.com/v2/middleware/weblogic/manifests/12.2.1.3: unauthorized: authentication required
```

Ensure the arguments you passed to the script `create-docker-credentials-secret.sh` are correct with respect to your Oracle SSO credentials.

The following example output shows the WebLogic domain was created successfully.
Expand Down Expand Up @@ -692,22 +692,22 @@ Now that we have created the AKS cluster, installed the operator, and verified t
service/domain1-cluster-1-external-lb created
```

After a short time, you will see the Administration Server and Managed Servers running.
After a short time, you will see the Administration Server and Managed Servers running.

Use the following command to check server pod status:

```bash
$ kubectl get pods --watch
```

It may take you up to 20 minutes to deploy all pods, please wait and make sure everything is ready.
It may take you up to 20 minutes to deploy all pods, please wait and make sure everything is ready.

You can tail the logs of the Administration Server with this command:

```bash
kubectl logs -f domain1-admin-server
```

The final example of pod output is as following:

```bash
Expand All @@ -719,7 +719,7 @@ Now that we have created the AKS cluster, installed the operator, and verified t
domain1-managed-server2 1/1 Running 0 3m56s
weblogic-operator-56654bcdb7-qww7f 1/1 Running 0 25m
```

{{% 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.
{{% /notice %}}

Expand Down Expand Up @@ -1001,11 +1001,11 @@ The logs are stored in the Azure file share. Follow these steps to access the lo
The output from the `create-domain-on-aks.sh` script includes a statement about the Azure resources created by the script. To delete the cluster and free all related resources, simply delete the resource groups. The output will list the resource groups, such as.

```bash
The following Azure Resouces have been created:
The following Azure Resouces have been created:
Resource groups: ejb8191resourcegroup1597641911, MC_ejb8191resourcegroup1597641911_ejb8191akscluster1597641911_eastus
```

Given the above output, the following Azure CLI commands will delete the resource groups.
Given the above output, the following Azure CLI commands will delete the resource groups.

```bash
az group delete --yes --no-wait --name ejb8191resourcegroup1597641911
Expand Down