Skip to content

Commit 785716e

Browse files
committed
Update Blog “exposing-an-application-using-ingress-and-tls-termination-on-kubernetes-in-hpe-greenlake-for-private-cloud-enterprise”
1 parent 78423ef commit 785716e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

content/blog/exposing-an-application-using-ingress-and-tls-termination-on-kubernetes-in-hpe-greenlake-for-private-cloud-enterprise.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ NAME IPADDRESSPOOLS IPADDRESSPOOL SELECTORS INTERFACES
8585
cfe-l2advert ["cfe-pool"]
8686
```
8787

88-
### Deploy Ngnix ingress controller
88+
### Deploy Ngnix Ingress controller
8989

9090
```shell
9191
$ helm upgrade --install ingress-nginx ingress-nginx \
@@ -366,6 +366,7 @@ spec:
366366
number: 80
367367
```
368368

369+
369370
In the above sample YAML manifest file, there is the *tls block* that contains the hostname *'nginx.example.com'* and the tls secret *cfe-tls-key-pair* created in the certification steps. There is also the *rules block* in which a list of routing rules is defined per host, e.g., host *nginx.example.com* will be routed to the application service *nginx-main* in the backend.
370371

371372
Type the following command to deploy the Ingress resource to the namespace *nginx-apps*:

0 commit comments

Comments
 (0)