Make Canary Releases Optional in LMOS-Operator

[bharatnpti]

Description
The traffic-splitting feature in the LMOS-Operator is currently a core functionality. However, making this feature optional could enhance flexibility for users who want to utilize the LMOS ecosystem without depending on Istio or traffic-splitting capabilities. This change would allow the operator to function in environments where Istio is not installed or required.

Rationale

• Increased Flexibility: Some users may not need traffic-splitting or may use alternative mechanisms for managing traffic within their Kubernetes clusters.
• Simpler Setup: Making traffic-splitting optional would lower the barrier for adoption, especially for teams that do not use Istio.
• Broader Use Cases: Users with simpler channel management needs could still leverage LMOS-Operator without needing advanced deployment strategies.

Proposed Solution

• Introduce a configuration flag or parameter that enables or disables traffic-splitting during the operator's installation:
• Add a Helm chart value, e.g., enableTrafficSplitting: true/false.
• When set to false, the operator should:
• Avoid creating Istio VirtualService resources.
• Handle channel routing logic without traffic-splitting features.
• Ensure that the operator continues to resolve channels and capabilities seamlessly even when traffic splitting is disabled.

[RobWin]

Hello,
I like the idea to make it optional.
But we should stick with a different term "enableCanaryReleases" not "enableTrafficSplitting".