Mukul SharmaandClaude Opus 5
f703f0b55a
Each of these now answers on <name>.infra.deployshed.com alongside the nip.io name it already had. Both are kept on purpose: nothing that currently references the old name breaks, and the new one can be proved before anything depends on it. Removing nip.io is a separate step, and a larger one, because Harbor's name is embedded in every running app's image reference. TLS covers the real domain only. Let's Encrypt cannot issue for nip.io — it is not on the public suffix list and every *.nip.io certificate shares one rate limit — so a tls block naming both would request one certificate spanning them and receive nothing for either. Each tls block therefore lists exactly the one new hostname, which is why they are written out rather than derived from the host list beside them. The charts disagree about how to express a second host, so each is done the way its own chart supports: gitea, grafana, vault, victoria-metrics-single take host lists, so the new name joins the existing one on a single Ingress. jenkins' primary ingress accepts exactly one hostName, so the new name goes on secondaryingress — a whole second Ingress object at the same backend. paths must be set explicitly there; left at the chart's default of [] it renders zero routes and the hostname answers nothing. argo-cd takes extraHosts natively, but its ingress.tls is a boolean bound to one fixed secret covering every host at once. Turning it on would request a certificate including nip.io and fail, and there is no extraTls to scope it. So ArgoCD gains the hostname now and its certificate when nip.io goes. Harbor is untouched here. It has no multi-host mechanism at all, so its second hostname needs a standalone Ingress, and its externalURL is what docker clients are handed — both deserve their own change rather than riding along with a hostname tidy-up. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N
42 lines
1.3 KiB
YAML
42 lines
1.3 KiB
YAML
victoria-metrics-single:
|
|
server:
|
|
# 7 days rather than the chart's month: this cluster exists to prove a
|
|
# pipeline, and every extra day is disk against the project's 250GB SSD
|
|
# quota, which every standard-rwo volume in the cluster shares.
|
|
retentionPeriod: "7d"
|
|
|
|
persistentVolume:
|
|
storageClassName: standard-rwo
|
|
# VictoriaMetrics' compression is why it replaced Prometheus here;
|
|
# this cluster's metric volume at 7 days fits well inside 3Gi. Unlike
|
|
# the homelab's local-path, this class can be expanded later.
|
|
size: 3Gi
|
|
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 128Mi
|
|
limits:
|
|
memory: 512Mi
|
|
|
|
# vmui, VictoriaMetrics' built-in query UI, on the same pod and port —
|
|
# ad-hoc PromQL only, no saved dashboards; Grafana is the real UI. Free
|
|
# to expose, since it is not a separate component.
|
|
ingress:
|
|
enabled: true
|
|
ingressClassName: contour
|
|
annotations:
|
|
# Certificate for the real domain only; nip.io cannot have one.
|
|
cert-manager.io/cluster-issuer: letsencrypt-prod
|
|
hosts:
|
|
- name: vm.35.238.248.203.nip.io
|
|
path: ["/"]
|
|
port: http
|
|
- name: vm.infra.deployshed.com
|
|
path: ["/"]
|
|
port: http
|
|
tls:
|
|
- secretName: vm-tls
|
|
hosts:
|
|
- vm.infra.deployshed.com
|