Update cluster-ingress-operator to install and manage Istio without using an OLM subscription.

Epic Goal

Remove the dependency on OLM and the risk of conflict with a customer-created OLM subscription for OSSM.

Note that the goal of this epic is not necessarily to remove the dependency on OSSM and Sail Operator per se. However, the most viable approach to removing the dependency on the OLM subscription may be to have cluster-ingress-operator directly manage Istio using Helm charts instead of using an Istio CR and relying on Sail Operator.

Why is this important?

The current approach of installing OSSM using an OLM subscription causes several problems:

• If the cluster-admin has already created an OLM subscription for OSSM, it can prevent cluster-ingress-operator from installing the version of OSSM/Istio that it needs.
• If the cluster-admin wants to create an OLM subscription for OSSM with a different version than what cluster-ingress-operator has installed, we do not have a clear, supportable solution.
• If the cluster does not have OLM and the Marketplace capabilities enabled, cluster-ingress-operator cannot install OSSM using an OLM subscription.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status:

• Priority is set by engineering
• Epic must be Linked to a Parent Feature
• Target version must be set
• Assignee must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? Have they been notified? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

1.

...

Previous Work (Optional)

1. …

Open questions

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>