Goal
The goal of this user story is to describe the implementation details and alternative approaches for making the ingress operator optional. Main points to be described:

• ingress operator's capability (ies): route-api, gateway api
• usage of the cluster capability vs some other ingress configuration
• target platform requirement and differences: hypershift vs standalone
• all components dependent on the ingress operator

HyperShift engineering prefers the cluster capability to be the main mechanism for the ingress operator disabling/enabling. Same point is expressed by Ben Parees and generally agreed by the NetworkEdge team.

Out of scope

• Create a full fledged EP. The procedure of how to implement a new capability is already defined and described. This EP has to describe the specifies of the ingress operator and the alternatives in a form which can be easily reviewed (GitHub PR).

Acceptance criteria

• EP is approved and merged

Links

• Slack thread which discusses the need of the EP due to the complexity of the task.