feat: integrate gateway api endpoint for chart deployment

[tboerger]

Description of the change

The Gateway API had been established as the new standard as an alternative for Ingress resources. With this change it's possible to deploy the HTTPRoute resource directly as part of the chart.

Existing or Associated Issue(s)

None

Additional Information

None

Checklist

• Chart version bumped in Chart.yaml according to semver.
• Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
• JSON Schema generated.
• List tests pass for Chart using the Chart Testing tool and the ct lint command.

[ChrisJBurns]

@tboerger Thanks for this, could you perhaps add a CI test for the gateway api resources?

[tboerger]

Sure, let me check that.

[tboerger]

I have added charts/backstage/ci/httproute-values.yaml now.

[tboerger]

I have checked everything with pre-commit now, it should be fine :)

[tumido]

Hi @tboerger thank you for opening your PR! 🙌

I 💯 agree with you that Backstage chart should have support for Gateway, it's a great addition.

However it seems our CI is not currently ready. This is not an issue with your PR by itself, yet it is still required to adjust the test setup before we can merge your PR.

The issue is that we use a Kind cluster to test the chart and this cluster has no Gateway provider.

I suggest we extend it with
https://github.com/kubernetes-sigs/cloud-provider-kind

(see: https://kubernetes.io/blog/2026/01/28/experimenting-gateway-api-with-kind/ )

Here is where we need to extend the workflow:

charts/.github/workflows/test.yml

Lines 45 to 55 in 38a8122

	- name: Create KIND Cluster
	if: steps.list-changed.outputs.changed == 'true'
	uses: helm/kind-action@ef37e7f390d99f746eb8b610417061a60e82a6cc # pin@v1.14.0
	- name: Install Ingress Controller
	if: steps.list-changed.outputs.changed == 'true'
	run: "helm install ingress-nginx/ingress-nginx --generate-name --set controller.service.type='NodePort' --set controller.admissionWebhooks.enabled=false"
	- name: Run chart-testing (install)
	if: steps.list-changed.outputs.changed == 'true'
	run: ct install --config ct-install.yaml --target-branch "${{ github.event.pull_request.base.ref }}"

[tboerger]

@tumido I think it does not even need the kind cloud provider, it should be already enough to install the Gateway API CRDs to get the tests working as expected.

[tboerger]

Looks like this solved the testing :)

[tumido]

I think I found just one little deviation from the upstream core spec, otherwise LGTM. 🙌

[younsl]

Could kind and group be templatable (empty by default) for backendRefs?

When omitted, the controller fills in defaults and Argo CD reports the HTTPRoute as out-of-sync on every reconcile. See argoproj/argo-cd#22151.

[tboerger]

parentRefs is directly piped into toYaml, so you can define whatever you want.

Edit: just the name attribute per row is required.

[tboerger]

I have integrated the latest comment.

[ChrisJBurns]

Am happy to approve, did you want to put your green button stamp on it too @tumido

[tumido]

/lgtm
/approve

[tumido]

Sorry for the delay on my side, was caught by other work.. 🙂 Approved! Thank you! 👍