Skip to content

Commit 6ad2bdc

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

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,16 @@ the service type of *ClusterIP*, running on the port 80 over HTTP. Using cert-ma
2626

2727
### Overview
2828

29+
[HPE GreenLake for Private Cloud Enterprise: Containers](https://www.hpe.com/us/en/greenlake/containers.html), one of the HPE GreenLake cloud services available on the HPE GreenLake for Private Cloud Enterprise, allows customers to create a Kubernetes (K8s) cluster, view details about existing clusters, and deploy containerized applications to the cluster. It provides an enterprise-grade container management service using open source K8s.
30+
31+
32+
33+
After applications being deployed in the cluster, one common requirement is to expose the applications to be accessed securely over HTTPS. This requires to get a valid SSL/TLS certificate in K8s . Generating and managing SSL/TLS certificates in is not always easy. ….
34+
35+
36+
37+
This blog post, I
38+
2939
### Prerequisites
3040

3141
Before starting, make sure you have the following:

0 commit comments

Comments
 (0)