Skip to content

EPMDEDP-17177: feat: add HTTPRoute exposure to application Helm chart scaffold#292

Merged
SergK merged 1 commit into
masterfrom
add-support-for-envoy-for-apps
Jul 7, 2026
Merged

EPMDEDP-17177: feat: add HTTPRoute exposure to application Helm chart scaffold#292
SergK merged 1 commit into
masterfrom
add-support-for-envoy-for-apps

Conversation

@SergK

@SergK SergK commented Jul 7, 2026

Copy link
Copy Markdown
Member

Scaffolded applications can now be exposed via a Gateway API HTTPRoute as an alternative to nginx Ingress, driven by the platform-level gateway selection so no per-application change is required.

  • Thread the ingress controller type and parent Gateway (name/namespace) into the scaffold template config, resolved from the platform gateway selection at codebase creation
  • Render the httproute section when Envoy is selected and the ingress section otherwise, preserving the default hostname (-.), custom host and TLS options
  • Ship an HTTPRoute template attached to the shared Gateway, guarded nil-safely so the dormant exposure template never errors when its values section is absent
  • Drop the obsolete pre-1.19 Kubernetes version branching from the Ingress template
  • Keep Ingress the default for nginx clusters so existing applications and updates are unaffected

… scaffold

Scaffolded applications can now be exposed via a Gateway API HTTPRoute as an alternative
to nginx Ingress, driven by the platform-level gateway selection so no per-application
change is required.

- Thread the ingress controller type and parent Gateway (name/namespace) into the scaffold
  template config, resolved from the platform gateway selection at codebase creation
- Render the httproute section when Envoy is selected and the ingress section otherwise,
  preserving the default hostname (<name>-<namespace>.<wildcard>), custom host and TLS options
- Ship an HTTPRoute template attached to the shared Gateway, guarded nil-safely so the
  dormant exposure template never errors when its values section is absent
- Drop the obsolete pre-1.19 Kubernetes version branching from the Ingress template
- Keep Ingress the default for nginx clusters so existing applications and updates are unaffected

Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
@SergK SergK requested a review from a team as a code owner July 7, 2026 14:15
@SergK SergK merged commit f3a3d76 into master Jul 7, 2026
5 checks passed
@SergK SergK deleted the add-support-for-envoy-for-apps branch July 7, 2026 14:35
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