✨ Migrate from NGINX Ingress to Gateway API with NGINX Gateway Fabric

[MAVRICK-1]

This comprehensive migration replaces all NGINX Ingress resources with Gateway API equivalents:

Key Changes:

• Replace NGINX Ingress Controller with NGINX Gateway Fabric v2.3.0
• Implement Gateway API v1.4.1 with Gateway, GatewayClass, and HTTPRoute resources
• Add Gateway API reconcilers in pkg/reconcilers/shared/gateway.go
• Update all control plane reconcilers (k8s, k3s, ocm, vcluster) to use Gateway API
• Replace ingress.go with gateway.go across reconciler packages
• Update installation scripts to use NGINX Gateway Fabric
• Add HTTPS support with both HTTP (80) and HTTPS (443) listeners
• Remove all NGINX Ingress dependencies and resources
• Update documentation and test scripts

Fixes #601

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign pdettori for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[MAVRICK-1]

cc @clubanderson @MikeSpreitzer

[clubanderson]

@francostellari @MikeSpreitzer can you ptal? Maybe we can avoid the nginx support issues sooner than expected.

[MikeSpreitzer]

We need evidence that this works.

[MikeSpreitzer]

KubeFlex needs the routing into the hosting cluster to support TLS passthrough (https://github.com/kubestellar/kubeflex/blob/main/docs/users.md#install-kubeflex-on-an-existing-cluster). If I understand correctly, the Gateway API provides that only through a TLSRoute object --- which is not in the standard channel of the Gateway API.

[shivansh-source]

@MAVRICK-1 status ?

[clubanderson]

Hi @francostellari, this PR needs a rebase to resolve conflicts with the main branch. Could you please rebase and push?

git fetch origin
git rebase origin/main
git push --force-with-lease

Thanks!

[clubanderson]

Hi @MAVRICK-1 👋

This PR needs a rebase to resolve conflicts with the main branch. You can do this with:

git fetch origin
git rebase origin/main
# Resolve any conflicts if needed
git push --force-with-lease

Once rebased, the CI checks will run again. Let us know if you need any help!

[MAVRICK-1]

Hi @MAVRICK-1 👋

This PR needs a rebase to resolve conflicts with the main branch. You can do this with:

git fetch origin
git rebase origin/main
# Resolve any conflicts if needed
git push --force-with-lease

Once rebased, the CI checks will run again. Let us know if you need any help!

@clubanderson is that u , or AI generated ?