lux.safe + www.lux.safe are not real public TLDs, so Let's Encrypt can
never validate them. Because LE issues only when ALL identifiers in an
order validate, bundling them wedged the lux-safe-tls order in 'pending'
for 87 days even though safe.lux.network's own HTTP-01 challenge was
valid. Result: no lux-safe-tls Secret -> ingress served the default
cert -> safe.lux.network returned 000.
Leaving only safe.lux.network lets the order complete and the cert
issue. Same class of fix as 240a03d5 (dropped .bitcoin/.coin/.invest).
Co-authored-by: Hanzo Dev <[email protected]>
28 lines
610 B
YAML
28 lines
610 B
YAML
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
name: lux-safe
|
|
namespace: hanzo
|
|
labels:
|
|
app.kubernetes.io/managed-by: lux-universe
|
|
app.kubernetes.io/part-of: lux-safe
|
|
annotations:
|
|
cert-manager.io/cluster-issuer: letsencrypt-prod
|
|
spec:
|
|
ingressClassName: ingress
|
|
tls:
|
|
- hosts:
|
|
- safe.lux.network
|
|
secretName: lux-safe-tls
|
|
rules:
|
|
- host: safe.lux.network
|
|
http:
|
|
paths:
|
|
- path: /
|
|
pathType: Prefix
|
|
backend:
|
|
service:
|
|
name: lux-safe
|
|
port:
|
|
number: 80
|