Janik von Rotz
0c20e44e01
- Update all documentation guides (Exoscale, Infomaniak, K3s, Development, Backup) to use ingress-nginx instead of haproxy-ingress - Replace haproxy-ingress references in task commands and scripts with ingress-nginx equivalents - Update Helm chart configurations (hugo, nextcloud, odoo, taskfileBuild, vuepress) to use nginx ingress class - Modify ingress templates to include nginx-specific annotations and TLS configurations - Add ingress-nginx as an external chart and remove haproxy-ingress related code - Update Odoo chart to support python package installation and storage class configuration - Adjust cert-manager cluster issuers to use nginx ingress class name
Mint System Cluster Issuer
This chart deploys cluster issuers for prod and staging and for dns and http.
Secrets
To use the Infomaniak resolver setup a infomaniak-api-credentials secret with the API token.
INFOMANIAK_API_TOKEN="*******"
kubectl create secret generic infomaniak-api-credentials \
--from-literal=api-token="$INFOMANIAK_API_TOKEN" \
-n cert-manager
Test
Infomaniak webhook
To test the Infomaniak webhook create a certificate with the letsencrypt-dns-staging issuer.
echo "Apply certificate."
cat <<EOF | kubectl apply -f -
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: chk-mintcloud-ch
spec:
secretName: chk-mintcloud-ch
issuerRef:
name: letsencrypt-dns-staging
kind: ClusterIssuer
dnsNames:
- chk.mintcloud.ch
EOF
Parameters
Cluster Issuer parameters
| Name | Description | Value |
|---|---|---|
acme.email |
The email address for ACME | "" |
acme.solver |
The solver for ACME | "" |