radius-project / radius-project/roadmap

Remove dependency on Contour (customizable Ingress/Gateway controller)

Open
#58 0 comments 0 reactions 1 assignee View on GitHub

@willtsai is already working on this.

Since Apr 23, 2026.

Dominant language
No language data
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Overview of roadmap item

Today, Radius has a dependency on Contour as an Ingress/Gateway controller, but many users have expressed complex requirements around ingress that were scenario-specific. For example, some users already had a load balancer set up and didn't need another one just for Radius.

To address this, Radius should allow users to configure their choice of Ingress/Gateway using a Recipe, with Contour perhaps being the default implementation. When a gateway is created, the recipe can decide what infrastructure to configure, which helps decouple Radius from Contour and supports more kinds of controllers.

### Related issues
- [ ] https://github.com/radius-project/radius/issues/6521
- [ ] https://github.com/radius-project/radius/issues/6369

Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.