Skip to content

chore(errorpages): disable branded error pages by default - #62

Merged
ashishmax31 merged 1 commit into
mainfrom
chore/disable-branded-error-pages
Aug 4, 2026
Merged

chore(errorpages): disable branded error pages by default#62
ashishmax31 merged 1 commit into
mainfrom
chore/disable-branded-error-pages

Conversation

@ashishmax31

Copy link
Copy Markdown
Contributor

Summary

Turns off the Traefik branded error-page wiring in both charts.

  • stackdome-agent-standalone: errorPages.enabled defaults to false, so the Service, Middleware, and catch-all IngressRoute are no longer rendered.
  • stackdome-agent: drops the traefik.ports.{web,websecure}.middlewares references and sets the subchart flag to false.

Both changes have to move together. Traefik fails every router whose middleware does not resolve, so leaving the entrypoint references in place while the Middleware is gone would take cluster ingress down.

What was left alone

  • The agent still serves the pages on its error-pages port (idle listener, costs nothing).
  • templates/validate-error-page-middleware.yaml still renders — it no-ops when no reference names stackdome-errors.

Re-enabling is flipping the two flags back and restoring the entrypoint references to <release-namespace>-stackdome-errors@kubernetescrd.

Test plan

  • helm template charts/stackdome-agent-standalone — no error-page Service/Middleware/IngressRoute in the output (only the port comment on the Deployment remains).
  • helm lint charts/stackdome-agent-standalone — passes.

Turn off the Traefik error-page wiring in both charts:

- stackdome-agent-standalone: errorPages.enabled now defaults to false, so
  the Service, Middleware, and catch-all IngressRoute are no longer rendered.
- stackdome-agent: drop the entrypoint middleware references and set the
  subchart flag to false.

Both changes have to move together. A middleware reference that does not
resolve fails every router on that entrypoint, so leaving the references in
place while the Middleware is gone would take ingress down.

The agent still listens on the error-pages port and the middleware-reference
validator still renders, so re-enabling is a matter of flipping the two flags
back and restoring the entrypoint references.
@ashishmax31
ashishmax31 merged commit 0a69c23 into main Aug 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant