-
Notifications
You must be signed in to change notification settings - Fork 1
/
tls.yaml
38 lines (36 loc) · 1023 Bytes
/
tls.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
---
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
name: letsencrypt-staging
namespace: default
spec:
acme:
server: https://acme-staging-v02.api.letsencrypt.org/directory
email: [email protected]
privateKeySecretRef:
name: letsencrypt-staging
http01: {}
---
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
name: ambassador-certs
# cert-manager will put the resulting Secret in the same Kubernetes namespace
# as the Certificate. Therefore you should put this Certificate in the same namespace as Ambassador.
namespace: default
spec:
# naming the secret name certificate ambassador-certs is important because
# ambassador just look for THIS particular name
secretName: ambassador-certs
issuerRef:
name: letsencrypt-staging
kind: ClusterIssuer
dnsNames:
- kubamb.westeurope.cloudapp.azure.com
acme:
config:
- http01:
ingressClass: nginx
domains:
- kubamb.westeurope.cloudapp.azure.com