- Szycy
- 27 września 2026 23:46 UTC
- Autor
- Kamo
- Pochęt się
- 5ce1604
kamofamily.org, kamobusiness.com, kamopersonal.com and kamocommunity.org are registered and pointed at the cluster. Their apex and www now 301 to https://www.kamouniverse.com with path and query preserved, the same way kamouniverse.com and www forward to www.kamocrm.com. That forward still applies, so visitors currently end up on kamocrm.com after two hops. dev.<domain> is each audience's own site and is not affected. - **************** one redirectRegex middleware plus http and https IngressRoutes at priority 300, above marketing-route's www.* catch-all. ACME challenge paths are excluded on :80. - auto-cert: the eight apex/www hosts in STATIC_DOMAINS. Six already had certs through the apex allowance. kamobusiness.com has no apex A record yet, so its two issue through the periodic retry once it does. kubectl diff over every target of the Traefik step: only the three new objects differ, so the Traefik deployment is not rolled.