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/1.3/content/navigate/kubernetes/k8s-ingress-controller.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ When editing a route:
88
88
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
89
89
`Target Service Namespace` field and the port specified by the `Target Port` field. After the domain has been deployed, you can select the `Target Service`
90
90
value from the drop-down list of available services in the WebLogic Kubernetes Operator domain's namespace. After the `Target Service` is selected,
91
-
you can select the `Target Port` from the list of available ports in the selected target service.
91
+
you can select the `Target Port` from the list of available ports in the selected target service.
92
92
- Specify the `Transport Option` for the ingress route:
93
93
* Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
94
94
* Select `SSL terminate at ingress controller` for SSL
@@ -97,14 +97,14 @@ When editing a route:
97
97
* Enable `Is target service WebLogic Console?` if the target service is the `WebLogic Console` service.
98
98
* Select `SSL pass through` for SSL traffic to pass through the ingress
99
99
controller and then terminate at the target service.
100
-
* If you select this option, you must also specify a valid DNS value in 'Virtual Host', and all SSL traffic from
100
+
* If you select this option, you must also specify a valid DNS value in 'Virtual Host', and all SSL traffic from
101
101
the`Virtual Host` will be routed to the target service.
102
102
* Make sure that the `Target Port` supports SSL.
103
103
- Use the `Ingress Route Annotations` table to
104
104
add annotations to the ingress route, as needed. Do not remove any pre-populated annotations.
105
105
106
106
### Code View
107
-
The `Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
107
+
`Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
108
108
displays the YAML definitions of the routes to be added, if applicable.
109
109
110
110
If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
Copy file name to clipboardExpand all lines: documentation/staging/1.3/content/navigate/model.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
@@ -45,7 +45,7 @@ icon beside a field, a dialog appears with the option of setting the field to a
45
45
The variable will show up in both the model and the variables editor on the `Code View` page. Likewise, when adding an application, you supply the path to the EAR,
46
46
WAR, or JAR file (or directory); that path will be put in the archive editor on the `Code View` page.
47
47
48
-
Note that if you create a new model using the `Design View` pages, the `Design View` will insert the `AdminUserName` and `AdminPassword` fields
48
+
Note that if you create a new model using the `Design View` pages, then the `Design View` will insert the `AdminUserName` and `AdminPassword` fields
49
49
into the `domainInfo` section of the model with their values set to variables whose values you will need to provide.
50
50
This is intended to help you create a domain with all of the required fields.
Copy file name to clipboardExpand all lines: documentation/staging/1.3/content/navigate/verrazzano/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ to help you:
11
11
12
12
1.[Configure]({{< relref "/navigate/verrazzano/vz-client-config#client-configuration" >}}) your Kubernetes client (`kubectl`) to connect to the Kubernetes cluster.
-`Application Name` - The name of the Verrazzano application.
22
+
-`Application Namespace` - The Kubernetes namespace to which the application will be deployed.
23
+
-`Application Version` - The version annotation value to add to the Verrazzano application.
24
+
-`Application Description` - The description annotation value to add to the Verrazzano application.
25
+
-`Verrazzano Version` - Provide the installed Verrazzano version. Click the icon to retrieve the value from the environment.
26
+
-`Use Multicluster Application` - Select whether to make this a multicluster application.
27
+
-`Create Verrazzano Project` - To deploy a multicluster application, a Verrazzano Project that includes the current application's namespace must exist. Select whether to create
28
+
a new Verrazzano Project.
29
+
-`Secret Names` - The secret names in the current namespace to associate with the application. To edit this field, click `Choose Secrets`.
30
+
-`Verrazzano Clusters for Application Placement` - The Verrazzano cluster names where the application should be placed. To edit this field, click `Choose Verrazzano Clusters`.
32
31
33
-
#### Ingress Controller Configuration
34
-
The most important field in this pane is the `Ingress Provider` field. This fields tells the WKT UI application with which of the
35
-
supported ingress controllers it will need to work. The current release supports two ingress
36
-
controllers:
32
+
#### Components
37
33
38
-
- NGINX
39
-
- Traefik
40
-
41
-
To install the ingress controller, enable `Install Ingress Controller`.
42
-
- To set the release name used by the Helm install process, use the `Helm Release Name to Use` field.
43
-
- Set the Kubernetes namespace to which the ingress controller should be installed with the `Ingress Controller Namespace` field.
44
-
45
-
The container image for the Traefik ingress controller resides in Docker Hub. Due to changes made
46
-
to Docker Hub, anonymous pull requests are throttled. This can result in pull requests being denied when the Kubernetes
47
-
cluster attempts to pull the image and start the container.
48
-
- To work around this limitation, enable the `Use Docker Hub Secret` field to provide login credentials for Docker Hub.
49
-
- The `Docker Registry Secret Name` field specifies the name of the Kubernetes pull secret to use when pulling the image.
50
-
To create this secret, enable `Create Docker Hub Secret` and fill in the pull secret data in the `Docker Hub Username`, `Docker Hub Password`,
51
-
and `Docker Hub Email Address` fields.
52
-
- For the NGINX ingress controller, if you want to have SSL pass through the ingress route, enable `Allow SSL pass through to target service`.
53
-
54
-
#### TLS Secret for Ingress Routes
55
-
Use this pane to configure the Transport Layer Security (TLS) secret containing the certificate and private key data that will be used by the
56
-
ingress controller when establishing HTTPS connections from clients to the ingress controller. The TLS connection will be
57
-
terminated at the ingress controller, so traffic between the ingress controller and services/pods will not be encrypted.
58
-
In the current release, only a single TLS certificate is supported for the routes being defined.
59
-
60
-
- To use TLS-enabled routes, enable `Use Ingress TLS Secret` and provide the secret name using the
61
-
`Ingress TLS Secret Name` field.
62
-
- To have the application create this secret, enable `Create Ingress TLS Secret`.
63
-
- If you already have a certificate file and its corresponding private key file, then use the `TLS Certificate File`
64
-
and `TLS Private Key File` fields to provide them.
65
-
- To create these files automatically, enable `Generate a TLS Certificate and Private Key`.
66
-
- Provide the path to the OpenSSL executable using the
67
-
`OpenSSL Executable to Use` field.
68
-
- Use the `Subject to Use for the Generated TLS Certificate` field to specify the data
69
-
to put into the subject of the certificate.
70
-
- For example, if your ingress route will use the virtual host name
71
-
`www.myapp.com`, you might specify the subject contents as `/CN=www.myapp.com`.
72
-
- The subject data will support multiple
73
-
key/value pairs using a comma-separated syntax, like `/key1=value1,/key2=value2,/key3=value3`.
74
-
75
-
#### Ingress Routes Configuration
76
-
Use the table in this section to define the ingress routes to be added by the application. _Note that this table does
77
-
not currently display existing routes already defined._ Any routes defined in or removed from the table will happen in
78
-
the WKT Project object. When applying or updating the routes, only the fields currently in the table will be considered.
79
-
If the routes do not exist, then they will be added. If one or more of the routes already exists, then the application will warn
80
-
you to confirm whether you want to update the existing route or routes before performing the operation.
81
-
82
-
To add a new route, click the plus (`+`) button in the table header. To edit a route, use the edit button on the corresponding
83
-
route row. To remove a route, use the delete icon on the corresponding route row.
84
-
85
-
When editing a route:
86
-
- Use the `Name` field to set the route name.
87
-
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
88
-
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
89
-
`Target Service Namespace` field and the port specified by the `Target Port` field. After the domain has been deployed, you can select the `Target Service`
90
-
value from the drop-down list of available services in the WebLogic Kubernetes Operator domain's namespace. After the `Target Service` is selected,
91
-
you can select the `Target Port` from the list of available ports in the selected target service.
92
-
- Specify the `Transport Option` for the ingress route:
93
-
* Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
94
-
* Select `SSL terminate at ingress controller` for SSL
95
-
terminating
96
-
at the ingress controller and then unencrypted traffic from the ingress controller to the target service.
97
-
* Enable `Is target service WebLogic Console?` if the target service is the `WebLogic Console` service.
98
-
* Select `SSL pass through` for SSL traffic to pass through the ingress
99
-
controller and then terminate at the target service.
100
-
* If you select this option, you must also specify a valid DNS value in 'Virtual Host', and all SSL traffic from
101
-
the`Virtual Host` will be routed to the target service.
102
-
* Make sure that the `Target Port` supports SSL.
103
-
- Use the `Ingress Route Annotations` table to
104
-
add annotations to the ingress route, as needed. Do not remove any pre-populated annotations.
105
34
106
35
### Code View
107
-
The `Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
36
+
`Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
108
37
displays the YAML definitions of the routes to be added, if applicable.
109
38
110
39
If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
@@ -115,18 +44,13 @@ set environment variables to specify any credentials required by the script to e
115
44
the script itself. This change is left as an exercise for you because different environments typically will have
116
45
existing standards for securely handling such credentials.
117
46
118
-
### Install Ingress Controller
119
-
`Install Ingress Controller` creates any namespace and secret specified and runs the ingress controller's Helm
120
-
chart to install the ingress controller. You access this action by using the `Install Ingress Controller` button on the
121
-
`Ingress Controller` page or the `Go` > `Install Ingress Controller` menu item.
122
-
123
-
### Update Ingress Routes
124
-
`Update Ingress Routes` creates the TLS secret, if needed, and adds or updates the specified ingress routes. You access this action
125
-
by using the `Update Ingress Routes` button on the `Ingress Controller` page or
126
-
the `Go` > `Update Ingress Routes to Domain` menu item.
47
+
### Deploy Application
48
+
`Deploy Application` creates the Domain custom resource object and any of its dependent objects (for example,
49
+
namespace, secrets, ConfigMap) in Kubernetes. You access this action by using the `Deploy Domain` button on the
50
+
`WebLogic Domain` page or the `Go` > `Deploy WebLogic Domain to Kubernetes` menu item.
127
51
128
-
### Uninstall Ingress Controller
129
-
`Uninstall Ingress Controller` uses the `helm uninstall` command to remove all the ingress resources
130
-
and uninstall the ingress controller. In addition, you can choose whether to also delete the corresponding namespace.
131
-
You access these actions by using the `Uninstall Ingress Controller` button on the
132
-
`Ingress Controller` page or the `Go` > `Uninstall Ingress Controller` menu item.
52
+
### Undeploy Application
53
+
`Undeploy Application` removes the Kubernetes custom resource for the WebLogic domain and its
54
+
dependent objects in Kubernetes. In addition, you can choose whether to also delete the corresponding namespace.
55
+
You access these actions by using the `Undeploy Domain` button on the
56
+
`WebLogic Domain` page or the `Go` > `Undeploy WebLogic Domain to Kubernetes` menu item.
0 commit comments