Document how to replace the default Gateway provider

[willdavsmith]

Scope

Add documentation that shows platform teams how to replace Radius' default Gateway provider.

Radius now installs and configures a default Contour Gateway for Radius.Compute/routes recipes when Contour installation is enabled. This issue tracks documenting the opt-out and replacement path for teams that want to use another Gateway API provider.

Documentation should cover

• Installing Radius without the default Contour install:

  rad install kubernetes --skip-contour-install

• Installing and configuring another Gateway API provider, such as NGINX Gateway Fabric.

• Creating a Kubernetes Gateway for Radius routes.

• Registering a recipe pack that uses the default Radius.Compute/routes recipe with provider-specific parameters:

  • gatewayName
  • gatewayNamespace

• Deploying an application with Radius.Compute/containers and Radius.Compute/routes.

• Verifying traffic through the replacement Gateway provider.

Non-goals

• Do not track the default Contour Gateway implementation here; that work is already done.
• Do not track removal of Contour from the default Radius install here.
• Do not introduce or document a Radius.Compute/gateways resource type.

Related work

• Docs PR: Add NGINX Gateway Fabric routes guide docs#1920
• Demo repository: https://github.com/willdavsmith/radius-nginx-demo

[radius-triage]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview