Skip to content

Commit 6b3ca66

Browse files
committed
Update Blog “exposing-an-application-using-ingress-and-tls-termination-on-kubernetes-in-hpe-greenlake-for-private-cloud-enterprise”
1 parent 627d736 commit 6b3ca66

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

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

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ replicaset.apps/ingress-nginx-controller-548768956f 1 1 1
157157

158158
The service *ingress-nginx-controller* gets deployed as the service type of *LoadBalancer* with the *EXTERNAL-IP* assigned as *10.6.115.251*.
159159

160-
### Install cert-manager
160+
### Generate a self-signed certificate using cert-manager
161161

162162
```shell
163163
$ kubectl get all -n cert-manager
@@ -238,11 +238,9 @@ NAME TYPE DATA AGE
238238
cfe-tls-key-pair kubernetes.io/tls 3 2m25s
239239
```
240240

241-
### Install Nginx applications
241+
### Deploy sample Nginx applications
242242

243-
Three Nginx applicaitons from the GitHub repo [ingress-demo](https://github.com/GuopingJia/ingress-demo.git) will be deployed as sample applications to the cluster.
244-
245-
The repo's *apps* folder contains the Nginx applications' YAML manifest files:
243+
In order to validate the Ingress TLS termination, three sample Nginx applications will be deployed to the cluster using the YAML manifest files from GitHub repo [ingress-demo](https://github.com/GuopingJia/ingress-demo):
246244

247245
```shell
248246
$ tree ingress-demo/
@@ -256,6 +254,8 @@ ingress-demo/
256254
└── README.md
257255
```
258256

257+
Each YAML manifest file in the folder *apps* defines the *Deployment* and the *Service* resource.
258+
259259
Type the following commands to deploy those Nginx applications to the namespace *nginx-apps*:
260260

261261
```shell
@@ -271,7 +271,7 @@ service/nginx-blue created
271271
deployment.apps/nginx-blue created
272272
```
273273

274-
Check with below command to see that all the Nginx Pods are in Running state:
274+
Type the command shown below to check the details of application deployment:
275275

276276
```shell
277277
$ kubectl get all -n nginx-apps
@@ -296,6 +296,9 @@ replicaset.apps/nginx-green-8956bbd9f 1 1 1 24s
296296
replicaset.apps/nginx-main-64bfd77895 1 1 1 32s
297297
```
298298

299+
Three Nginx applications, *nginx-main*, *nginx-blue* and *nginx-green*, are deployed as the service type of *ClusterIP*. They provide internal connectivity and can solely be accessed from within the cluster.
300+
301+
299302
Type the following commend to check that all the application service endpoints have been populated:
300303

301304
```shell

0 commit comments

Comments
 (0)