Ingress and Base Path

The frontend chart (charts/ska-octopus-frontend) is designed to run behind an ingress controller and under an optional sub-path. This page explains how the base path is derived, how to override it, and why the helper names are namespaced.

Defaults

  • ingress.paths.frontend controls the path prefix. When unset, the chart defaults to /<namespace>/<release> (e.g., /octopus/ska-octopus-frontend).

  • The same base path is injected into:

    • The ingress rule (path: <basePath>(/|$)(.*) with rewrite).

    • The nginx config map rewrite that flattens the prefix for direct Service access.

    • The BASE_PATH and VITE_BASE_PATH environment variables used by the entrypoint and the built assets.

Example override:

ingress:
  enabled: true
  host: octopus.example.org
  paths:
    frontend: /octopus

This renders ingress routes like https://octopus.example.org/octopus/....

Namespaced helpers

Helm template names are global. To avoid collisions with the backend chart, the frontend chart exposes ska-octopus-frontend.basePath (and matching *.name/*.fullname). This ensures the frontend always reads ingress.paths.frontend even when deployed alongside other Octopus charts.

Tips for suite deployments

  • Use the same path for frontend and backend (set both ingress.paths.frontend and ingress.paths.backend in your values file) so the UI and API share a predictable prefix.

  • Keep BASE_PATH and the ingress path aligned; they are wired from the same value by the chart.