-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find certificates to serve TLS #29
Comments
Do we have to mount the TLS cert/key using a secret ? |
As of now Directory: Line 53 in a27b696
Filenames: Lines 140 to 141 in a27b696
In Kubernetes I did the following - I use cert-manager for apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: kuard
name: kuard
namespace: foobar
spec:
replicas: 1
selector:
matchLabels:
app: kuard
template:
metadata:
labels:
app: kuard
spec:
containers:
- image: nexus-docker.cntr.swsnet.ch/kuar-demo/kuard-amd64:blue
name: kuard-amd64
ports:
- containerPort: 8080
name: http
protocol: TCP
- containerPort: 8443
name: https
protocol: TCP
volumeMounts:
- name: certificates
mountPath: /tls
readOnly: true
volumes:
- name: certificates
secret:
secretName: kuard-certificate
items:
- key: tls.crt
path: kuard.crt
- key: tls.key
path: kuard.key
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: kuard-certificate
namespace: foobar
spec:
secretName: kuard-certificate
commonName: kuard
privateKey:
algorithm: ECDSA
rotationPolicy: Always
size: 384
usages:
- digital signature
- key encipherment
- server auth
dnsNames:
- localhost
- kuard
- kuard.foobar
- kuard.foobar.svc
- kuard.foobar.svc.cluster.local
issuerRef:
name: ca-issuer
kind: ClusterIssuer |
Started the container (
docker run --rm -p 8080:8000 kuart
) and got the following outputAny ideas what needs to be in place for this to work?
The text was updated successfully, but these errors were encountered: