deep-stack/kompose
4
0
Fork 0
forked from LaconicNetwork/kompose
Code Pull Requests Activity

Add kompose.service.expose.tls-secret

Browse Source
This commit is contained in:
Oliver Bristow
2017-12-18 15:56:38 +00:00
committed by Oliver Bristow
parent e4adfef9cb
commit 35a782024d
8 changed files with 284 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide.md
+4 -1
View File
@@ -313,6 +313,7 @@ services:
- kompose.service.expose defines if the service needs to be made accessible from outside the cluster or not. If the value is set to "true", the provider sets the endpoint automatically, and for any other value, the value is set as the hostname. If multiple ports are defined in a service, the first one is chosen to be the exposed.
- For the Kubernetes provider, an ingress resource is created and it is assumed that an ingress controller has already been configured.
- For the OpenShift provider, a route is created.
- kompose.service.expose.tls-secret provides the name of the TLS secret to use with the Kubernetes ingress controller. This requires kompose.service.expose to be set.
For example:
@@ -327,6 +328,7 @@ services:
- redis
labels:
kompose.service.expose: "counter.example.com"
kompose.service.expose.tls-secret: "example-secret"
redis:
image: redis:3.0
ports:
@@ -338,7 +340,8 @@ The currently supported options are:
| Key | Value |
|----------------------|-------------------------------------|
| kompose.service.type | nodeport / clusterip / loadbalancer |
| kompose.service.expose| true / hostname |
| kompose.service.expose | true / hostname |
| kompose.service.expose.tls-secret | secret name |
**Note**: `kompose.service.type` label should be defined with `ports` only, otherwise `kompose` will fail.