change domain in hope of getting a valid certificate challenge respons

This commit is contained in:
2024-01-10 10:40:39 +01:00
parent b826035b3a
commit c5eddcab88
2 changed files with 6 additions and 6 deletions
+4 -4
View File
@@ -6,7 +6,7 @@ metadata:
annotations: annotations:
# nginx.ingress.kubernetes.io/force-ssl-redirect: "true" # nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
# nginx.ingress.kubernetes.io/backend-protocol: "HTTP" # nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
cert-manager.io/issuer: letsencrypt-kemkas cert-manager.io/issuer: letsencrypt-kemkas-staging
spec: spec:
ingressClassName: nginx ingressClassName: nginx
rules: rules:
@@ -19,8 +19,8 @@ spec:
name: kemkas-service name: kemkas-service
port: port:
number: 8080 number: 8080
host: dev.kemkas.hu host: staging.kemkas.hu
tls: tls:
- hosts: - hosts:
- dev.kemkas.hu - staging.kemkas.hu
secretName: letsencrypt-kemkas secretName: letsencrypt-kemkas-staging
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: cert-manager.io/v1 apiVersion: cert-manager.io/v1
kind: Issuer kind: Issuer
metadata: metadata:
name: letsencrypt-kemkas name: letsencrypt-kemkas-staging
namespace: kemkas namespace: kemkas
spec: spec:
# ACME issuer configuration # ACME issuer configuration
@@ -12,7 +12,7 @@ spec:
email: developer@kemkas.hu email: developer@kemkas.hu
server: https://acme-v02.api.letsencrypt.org/directory server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef: privateKeySecretRef:
name: letsencrypt-kemkas-private-key name: letsencrypt-kemkas-staging-private-key
solvers: solvers:
# Use the HTTP-01 challenge provider # Use the HTTP-01 challenge provider
- http01: - http01: