Skip to content

Commit 61d8200

Browse files
committed
Update Blog “generating-self-signed-certificates-using-cert-manager-for-kubernetes-in-hpe-greenlake-for-private-cloud-entreprise”
1 parent e4ed10d commit 61d8200

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/blog/generating-self-signed-certificates-using-cert-manager-for-kubernetes-in-hpe-greenlake-for-private-cloud-entreprise.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -428,7 +428,9 @@ $ k apply -f ingress-nginx-selfsigned.yaml -n cfe-apps
428428
ingress.networking.k8s.io/nginx-ingress-selfsigned created
429429
```
430430

431-
After deploying the Ingress using the above command, together with Nginx deployment, to the namespace *cfe-apps*, you can validate the Ingress TLS using the browser by typing the URL *nginx.example.com*. The browser will show a warning *Your connection is not private*:
431+
After deploying the Ingress using the above command, together with Nginx deployment, to the namespace *cfe-apps*, you can validate the Ingress TLS using the browser. Type the URL *nginx.example.com* in the browser, it will be rediected over HTTPS with the warning message *'Your connection is not private'*:
432+
433+
Start the browser and type the URL *nginx.example.com*, it will be rediected over HTTPS with the warning message *'Your connection is not private'*:
432434

433435
![](/img/nginx-private.png)
434436

0 commit comments

Comments
 (0)