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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,7 @@ Please refer to [Shutting down a domain](site/shutdown-domain.md) for informatio
161
161
162
162
## Load balancing with an Ingress controller or a web server
163
163
164
-
You can choose a load balancer provider for your WebLogic domains running in a Kubernetes cluster. Please refer to Load balancing with Voyager Ingress Controller, [Load balancing with Traefik Ingress Controller](site/traefik.md), and [Load balancing with Apache Web Server](site/apache.md) for information about the current capabilities and setup instructions for each of the supported load balancers.
164
+
You can choose a load balancer provider for your WebLogic domains running in a Kubernetes cluster. Please refer to Load balancing with Voyager Ingress Controller, [Load balancing with Traefik Ingress Controller](site/traefik.md), and [Load balancing with Apache HTTP Server](site/apache.md) for information about the current capabilities and setup instructions for each of the supported load balancers.
165
165
166
166
167
167
[comment]: #(Exporting operator logs to ELK. The operator provides an option to export its log files to the ELK stack. Please refer to [ELK integration]site/elk.md for information about this capability.)
Copy file name to clipboardExpand all lines: site/k8s_setup.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,18 +11,18 @@ If you need some help setting up a Kubernetes environment to experiment with the
11
11
12
12
* Set up your own Kubernetes environment on bare compute resources on a cloud.
13
13
* Use you cloud provider's management console to provision a managed Kubernetes environment.
14
-
* Install Kubernetes on your own compute resources (i.e. "real" computers, outside a cloud).
14
+
* Install Kubernetes on your own compute resources (for example, "real" computers, outside a cloud).
15
15
16
16
"Development/test" options:
17
17
18
18
* Install [Docker for Mac](https://docs.docker.com/docker-for-mac/#kubernetes) and enable its embedded Kubernetes cluster (or register for the [Docker for Windows](https://beta.docker.com/form) beta and wait until Kubernetes is available there).
19
19
* Install [Minikube](https://github.com/kubernetes/minikube) on your Windows/Linux/Mac computer.
20
20
21
-
We have provided our hints and tips for several of these options in the sections below:
21
+
We have provided our hints and tips for several of these options in the sections below.
22
22
23
23
## Set up Kubernetes on bare compute resources in a cloud
24
24
25
-
Follow the basic steps from the [Terraform Kubernetes installer for Oracle Cloud Infrastructure](https://github.com/oracle/terraform-kubernetes-installer):
25
+
Follow the basic steps from the [Terraform Kubernetes installer for Oracle Cloud Infrastructure](https://github.com/oracle/terraform-kubernetes-installer).
4. Ensure you have [Kubectl][Kubectl] installed if you plan to interact with the cluster locally.
37
+
4. Ensure that you have [Kubectl][Kubectl] installed if you plan to interact with the cluster locally.
38
38
39
39
### Quick Start
40
40
@@ -50,13 +50,13 @@ cd terraform-kubernetes-installer
50
50
terraform init
51
51
```
52
52
53
-
3. Copy the example terraform.tvfars:
53
+
3. Copy the example `terraform.tvfars`:
54
54
55
55
```
56
56
cp terraform.example.tfvars terraform.tfvars
57
57
```
58
58
59
-
4. Edit the `terraform.tvfars` file to include values for your tenancy, user, and compartment. Optionally edit variables to change the `Shape` of the VMs for your Kubernetes master and workers, and your etcd cluster. For example:
59
+
4. Edit the `terraform.tvfars` file to include values for your tenancy, user, and compartment. Optionally, edit variables to change the `Shape` of the VMs for your Kubernetes master and workers, and your `etcd` cluster. For example:
60
60
61
61
```
62
62
#give a label to your cluster to help identify it if you have multiple
@@ -138,20 +138,20 @@ $
138
138
```
139
139
140
140
141
-
## Install Kubernetes on your own compute resources (e.g. Oracle Linux servers outside a cloud)
141
+
## Install Kubernetes on your own compute resources (for example, Oracle Linux servers outside a cloud)
142
142
143
-
These instructions are for Oracle Linux 7u2+. If you are using a different flavor of Linux, you will need to adjust accordingly.
143
+
These instructions are for Oracle Linux 7u2+. If you are using a different flavor of Linux, you will need to adjust them accordingly.
144
144
145
-
**NOTE** These steps must be run with the `root` user, until specified otherwise! Any time you see `YOUR_USERID` in a command, you should replace it with your actual userid.
145
+
**NOTE**: These steps must be run with the `root` user, until specified otherwise! Any time you see `YOUR_USERID` in a command, you should replace it with your actual `userid`.
146
146
147
-
Choose the directories where your Docker and Kubernetes files will be stored. The Docker directory should be on a disk with a lot of free space (more than 100GB) because it will be used for the `/var/lib/docker` file syste, which contains all of your images and containers. The Kubernetes directory will be used for the `/var/lib/kubelet` file system and persistent volume storage.
147
+
Choose the directories where your Docker and Kubernetes files will be stored. The Docker directory should be on a disk with a lot of free space (more than 100GB) because it will be used for the `/var/lib/docker` file system, which contains all of your images and containers. The Kubernetes directory will be used for the `/var/lib/kubelet` file system and persistent volume storage.
148
148
149
149
```
150
150
export docker_dir=/scratch/docker
151
151
export k8s_dir=/scratch/k8s_dir
152
152
```
153
153
154
-
Create a shell script that sets up the necessary environment variables. You should probably just append this to the user's `.bashrc` so that it will get executed at login. You will also need to configure your proxy settings in here if you are behind an HTTP proxy:
154
+
Create a shell script that sets up the necessary environment variables. You should probably just append this to the user's `.bashrc` so that it will get executed at login. You will also need to configure your proxy settings here if you are behind an HTTP proxy:
155
155
156
156
```
157
157
export PATH=$PATH:/sbin:/usr/sbin
@@ -186,14 +186,14 @@ If you want command completion, you can add the following to the script:
186
186
source <(kubectl completion bash)
187
187
```
188
188
189
-
Create the directories we need:
189
+
Create the directories you need:
190
190
191
191
```
192
192
mkdir -p $docker_dir $k8s_dir/kubelet
193
193
ln -s $k8s_dir/kubelet /var/lib/kubelet
194
194
```
195
195
196
-
Set an environment variable with the Docker version we want to install:
196
+
Set an environment variable with the Docker version you want to install:
**NOTE** The following steps should be run with your normal (non-`root`) user.
317
+
**NOTE**: The following steps should be run with your normal (non-`root`) user.
318
318
319
319
Configure CNI:
320
320
@@ -357,7 +357,7 @@ Congratulations! Docker and Kubernetes are installed and configured!
357
357
358
358
## Install Docker for Mac with Kubernetes
359
359
360
-
Docker for Mac 17.12 CE Edge provides an [embedded Kubernetes environment](https://docs.docker.com/docker-for-mac/#kubernetes) that is a pretty quick and easy way to get a simple test environment set up on your Mac. To set it up, follow these instructions:
360
+
Docker for Mac 17.12 CE Edge provides an [embedded Kubernetes environment](https://docs.docker.com/docker-for-mac/#kubernetes) that is a quick and easy way to get a simple test environment set up on your Mac. To set it up, follow these instructions:
361
361
362
362
Install "Docker for Mac" from the Edge channel [https://download.docker.com/mac/edge/Docker.dmg](https://download.docker.com/mac/edge/Docker.dmg). Then start up the Docker application (press Command-Space bar, type in `Docker` and run it). After it is running you will see the Docker icon appear in your status bar:
363
363
@@ -371,7 +371,7 @@ Go to the "Kubernetes" tab and click on the option to enable Kubernetes:
**Note** If you are behind an HTTP proxy, then you should also go to the "Proxies" tab and enter your proxy details.
374
+
**Note**: If you are behind an HTTP proxy, then you should also go to the "Proxies" tab and enter your proxy details.
375
375
376
376
Docker will download the Kuberentes components and start them up for you. When it is done, you will see the Kubernetes status go to green/running in the menu:
Copy file name to clipboardExpand all lines: site/manually-creating-domain.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Manually creating a WebLogic domain
2
2
3
-
**PLEASE NOTE** This page is a work in progress, we have some rough notes in here, we are working on writing better doc for how to set up this integration.
3
+
**PLEASE NOTE**: This page is a work in progress. We have some rough notes here and are working on writing better documentation for how to set up this procedure.
4
4
5
-
If creating the domain manually, using a WLST script for example, the domain must be configured to meet these requirements:
5
+
If you are creating the domain manually, for example, using a WLST script, the domain must be configured to meet these requirements:
6
6
7
7
* Domain directory should be in `/shared/domain`.
8
8
* Applications directory should be in `/shared/applications`.
@@ -11,11 +11,11 @@ If creating the domain manually, using a WLST script for example, the domain mus
11
11
12
12
## Use the scripts to create the sample YAML files
13
13
14
-
The `create-weblogic-domain.sh` script described in the previous section can be executed with the “-g” option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment. This is a useful way to create the sample YAML files needed to manually create a domain.
14
+
The `create-weblogic-domain.sh` script can be executed with the `-g` option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment. This is a useful way to create the sample YAML files needed to manually create a domain.
15
15
16
16
First, make a copy of `create-weblogic-domain-inputs.yaml` and customize it.
17
17
18
-
Next, choose and create a directory that generated operatorrelated files will be stored in, e.g. /path/to/weblogic-operator-output-directory
18
+
Next, choose and create a directory that generated operator-related files will be stored in, for example, `/path/to/weblogic-operator-output-directory`.
19
19
20
20
Then, execute the script, pointing it at your inputs file and output directory:
21
21
@@ -25,7 +25,7 @@ Then, execute the script, pointing it at your inputs file and output directory:
25
25
-o /path/to/weblogic-operator-output-directory
26
26
```
27
27
28
-
The following YAML files will be generated in the /path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID> directory:
28
+
The following YAML files will be generated in the `/path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID>` directory:
29
29
30
30
*`weblogic-domain-pv.yaml` can be customized and used to create the persistent volume for this domain.
31
31
*`weblogic-domain-pvc.yaml` can be customized and used to create the persistent volume claim for this domain.
@@ -48,13 +48,13 @@ The file `weblogic-domain-pv.yaml` contains a template to create a persistent vo
48
48
* Persistent volume name
49
49
* Storage class name
50
50
* The amount of storage to allocate
51
-
* The physical location of the persistent volume (edit). Prior to creating the persistent volume you need to ensure this location exists and has read/write/execute permission set for the account that Kubernetes is running from.
51
+
* The physical location of the persistent volume (edit). Prior to creating the persistent volume, you need to ensure this location exists and has read/write/execute permissions set for the account that Kubernetes is running from.
52
52
* The access mode is Read/Write Many. You must use a provider that supports Read/Write Many.
53
53
* The contents of the volume are retained across restarts of the Kubernetes environment.
54
54
55
55
## Creating the persistent volume
56
56
57
-
To create the persistent volume issue the following command:
57
+
To create the persistent volume, issue the following command:
58
58
59
59
```
60
60
kubectl create –f weblogic-domain-pv.yaml
@@ -70,7 +70,7 @@ Replace `PV_NAME` with the name of the persistent volume.
70
70
71
71
## Preparing to create the persistent volume claim
72
72
73
-
The file `weblogic-domain-pvc.yaml` contains a template to claim a portion of the persistent volume storage. The customizable items are listed below:
73
+
The file,`weblogic-domain-pvc.yaml`, contains a template to claim a portion of the persistent volume storage. The customizable items are:
74
74
75
75
* Persistent volume claim name
76
76
* Namespace name
@@ -80,7 +80,7 @@ The file `weblogic-domain-pvc.yaml` contains a template to claim a portion of th
80
80
81
81
## Creating the persistent volume claim
82
82
83
-
To create the persistent volume claim issue the following command:
83
+
To create the persistent volume claim, issue the following command:
84
84
85
85
```
86
86
kubectl create –f weblogic-domain-pvc.yaml
@@ -96,7 +96,7 @@ Replace `PVC_NAME` with the name of the persistent volume claim.
96
96
97
97
## Preparing to create the domain custom resource
98
98
99
-
The file `domain-custom-resource.yaml` contains a template to create the domain custom resource. The customizable items are listed below:
99
+
The file,`domain-custom-resource.yaml`, contains a template to create the domain custom resource. The customizable items are:
0 commit comments