Exploration: Route and Domain CRD Design

[acosta11]

Context / Background
To support the migration of CF routing functionality on Kubernetes, we would like to design an interface with which the CF API shim may interact. This interface both defines the schema used to store object data and acts as the input to the Kubernetes controller that will adapt the resources to other Kubernetes solutions.

Desired outcomes
A proposal for the api with a goal of initially supporting mvp cf push requirements and eventually supporting more granular domain management and validation. The team and community has a chance to provide feedback on the design.

Acceptance Criteria / Scenarios
As a member of community, I can view a proposal for the CF Route and Domain interfaces.

Timebox: 3 days

Notes
Given the purpose of the api as a replacement for the CCDB, we suspect the need for a Route and Domain resource. This may actually just re-use the prior art from the cf-k8s networking team with some novel exploration of how we might better prepare to manage domains and tenancy.

Focus on the Routes features supported by the V3 API (de-emphasizing Domain management) and ensure the interface supports that. One example to consider: will this design enable API endpoints that interact with a single route destination rather than all routes for an App?

Related Docs

cf-k8s-networking ADR for Route CR

cf-k8s-networking Route CR

cf-k8s-networking thoughts on updating Route CR

CAPI CRD explore doc

CF API V3 Docs

custom domains thoughts from eirini (more forward looking with domain management)

[acosta11]

See the exploration doc at: https://docs.google.com/document/d/1WUiFwMgKkZrHHbqL1sMuHdqempzfIiYXpnq6qoazVKc .

We would like an initial round of feedback on the two potential proposals contained therein.

@cloudfoundry/cf-k8s