1 parent
e1026b87db
commit
1e67a5d0f9
3 files changed
+8
-6
No files matched your search
@@ -177,8 +177,8 @@ spec:
|
|||||||
- metadata:
|
- metadata:
|
||||||
name: data
|
name: data
|
||||||
spec:
|
spec:
|
||||||
|
storageClassName: nfs-large
|
||||||
accessModes: ["ReadWriteOnce"]
|
accessModes: ["ReadWriteOnce"]
|
||||||
resources:
|
resources:
|
||||||
requests:
|
requests:
|
||||||
storage: 4Gi
|
storage: 4Gi
|
||||||
# storageClassName: <your default class>
|
|
||||||
@@ -12,6 +12,7 @@ metadata:
|
|||||||
k8s-helper.io/group: "Infrastructure"
|
k8s-helper.io/group: "Infrastructure"
|
||||||
k8s-helper.io/icon: "network"
|
k8s-helper.io/icon: "network"
|
||||||
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
|
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
|
||||||
|
cert-manager.io/cluster-issuer: letsencrypt-prod
|
||||||
# SSE (the live query log) is the reason for these three. With response
|
# SSE (the live query log) is the reason for these three. With response
|
||||||
# buffering on, nginx holds events until the buffer fills and the log page
|
# buffering on, nginx holds events until the buffer fills and the log page
|
||||||
# looks frozen; with a 60s read timeout the stream is cut every minute and
|
# looks frozen; with a 60s read timeout the stream is cut every minute and
|
||||||
@@ -22,7 +23,7 @@ metadata:
|
|||||||
spec:
|
spec:
|
||||||
ingressClassName: nginx
|
ingressClassName: nginx
|
||||||
rules:
|
rules:
|
||||||
- host: dns.example.com
|
- host: dns.k6n.net
|
||||||
http:
|
http:
|
||||||
paths:
|
paths:
|
||||||
# DoH must be matched before the catch-all below, and both are
|
# DoH must be matched before the catch-all below, and both are
|
||||||
@@ -50,7 +51,7 @@ spec:
|
|||||||
port:
|
port:
|
||||||
name: admin
|
name: admin
|
||||||
tls:
|
tls:
|
||||||
- hosts: [dns.example.com]
|
- hosts: [dns.k6n.net]
|
||||||
secretName: fancy-dns-tls
|
secretName: fancy-dns-tls
|
||||||
---
|
---
|
||||||
# Two replicas means one of them can always be taken away for a node drain.
|
# Two replicas means one of them can always be taken away for a node drain.
|
||||||
|
|||||||
+4
-3
@@ -20,9 +20,10 @@ Configure this repository's Gitea webhook for push events only:
|
|||||||
- Secret: the same value as `K8SHELPER_GITOPS_WEBHOOK_SECRET`
|
- Secret: the same value as `K8SHELPER_GITOPS_WEBHOOK_SECRET`
|
||||||
|
|
||||||
Bootstrap the GitOps resources once with `kubectl apply -f gitops/`. The
|
Bootstrap the GitOps resources once with `kubectl apply -f gitops/`. The
|
||||||
`dns` namespace is declared in the managed kustomization. Before bootstrapping,
|
`dns` namespace is declared in the managed kustomization. Before bootstrapping, create the `fancy-dns-apikey` Secret in `dns` with an
|
||||||
create `fancy-dns-apikey` in `dns` as described in `deploy/k8s/08-secret-apikey.yaml`
|
`api-key` entry. The ingress requests `dns.k6n.net` TLS from the
|
||||||
and ensure the cert-manager-managed `fancy-dns-tls` Secret exists. The GitOps
|
`letsencrypt-prod` ClusterIssuer and cert-manager creates `fancy-dns-tls`. The
|
||||||
|
StatefulSet PVCs use the `nfs-large` StorageClass. The GitOps
|
||||||
kustomization intentionally excludes both example Secret manifests so it never
|
kustomization intentionally excludes both example Secret manifests so it never
|
||||||
replaces real credentials or TLS material with placeholders.
|
replaces real credentials or TLS material with placeholders.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user