Skip to content

[CPCAP-16245] gate Ingress and HTTPRoute on GATEWAY_SYSTEM_TYPE - #233

Merged
DmitriiRabenok merged 2 commits into
mainfrom
fix/gateway-system-type
Oct 22, 2026
Merged

DmitriiRabenok merged 2 commits into
mainfrom
fix/gateway-system-type

Conversation

@pranavcracker

Copy link
Copy Markdown
Collaborator

Summary

Ingress and Gateway API resources are now controlled by the GATEWAY_SYSTEM_TYPE cloud passport parameter.

Problem

  • The Ingress was always created (ingress.create: true by default).
  • HTTPRoute/BackendTLSPolicy were created whenever the Gateway API CRDs existed in the cluster.

On Gateway API clusters this created both. So the deploy still depended on the ingress-nginx admission webhook even when nginx was disabled.

Changes

  • New GATEWAY_SYSTEM_TYPE parameter. It can hold comma-separated values and is checked with contains:

    Value Ingress HTTPRoute BackendTLSPolicy (tls.enabled) gateway-api-converter.netcracker.com/ignore on Ingress
    unset / legacy-ingress ✅ – – –
    gateway-api-default – ✅ ✅ –
    legacy-ingress,gateway-api-default ✅ ✅ ✅ ✅
  • ingress.create is kept as an additional off switch.

  • Removed the CRD / PAAS_PLATFORM auto-detection for the HTTPRoute and BackendTLSPolicy.

  • Added the standard app.kubernetes.io/* labels to the HTTPRoute and BackendTLSPolicy.

  • Added GATEWAY_SYSTEM_TYPE to values.yaml, values.schema.json and installation.md.

@pranavcracker

Copy link
Copy Markdown
Collaborator Author

@disa1217, please review doc updates.

@disa1217 disa1217 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @pranavcracker , I am ok with the doc updates.

@DmitriiRabenok
DmitriiRabenok merged commit be9a794 into main Oct 22, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants