apache / apache/openwhisk

How to set a custom certificate for the helm install?

Open
#5,499 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Scala
Stars
6.8k
Forks
1.2k
Avg merge
2d 14h
Merged PRs (30d)
2

Description

There is this:
```yaml
whisk:
# Ingress defines how to access OpenWhisk from outside the Kubernetes cluster.
# Only a subset of the values are actually used on any specific type of cluster.
# See the "Configuring OpenWhisk section" of the docs/k8s-*.md that matches
# your cluster type for details on what values to provide and how to get them.
ingress:
awsSSL: "false"
apiHostName: ""
apiHostPort: 31001
apiHostProto: "https"
type: NodePort
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: "50m"
domain: "domain"
tls:
enabled: false
secretenabled: false
createsecret: false
secretname: "ow-ingress-tls-secret"
secrettype: "type"
crt: "crt"
key: "key"
```
I have generated my own certificate.
But no matter what I set ```crt``` ,```key``` and ```enabled``` to, I still end up with the dreaded ```*.localhost"```.

Contributor guide

Open the contributing guide

Research direction

Start with the Helm values under whisk.ingress.tls and the matching docs/k8s-*.md configuration section. Trace how crt, key, enabled, and the secret settings are consumed during helm install. Done means a supplied custom certificate is used for ingress instead of the default *.localhost certificate.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
infrastructure, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.