Extend Istio CR with Egress

[strekm]

Description

Based on ADR extend Istio CR to support lifecycle Istio Egress component. There should be possibility to enable / disable component. There should be possibility to configure kubernetes properties of Istio Egress. Configuration should be validated to avoid misconfigurations.
Adding e2e tests is not in scope of this issue.

Reasons

Provide managed and configurable Istio Egress

Contact

ToDos [Developer]

• Extend Istio API with Egress gateway
• Extend Istio operator YAMLs templating to support Egress
• Extend existing integration test to verify resource configuration for egress is applied
• Extend existing operator documentation if necessary
• Add restart of egress gateway (consider ingress gateway restart criteria)

PRs

• Extend Istio CR with Egress Gateway #1178
• Add egress-gateway affinity #1196
• Fix egress resources #1197
• Set the same resources for egress and ingress #1198

ACs [PO]

• Egress should be disabled by default
• Egress can be enabled / disabled
• Egress can be configured
• Egress configuration is validated
• Egress reconciliation is included in Istio CR status

DoD [Developer & Reviewer]

• Provide unit and integration tests.
• Provide documentation.
• Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
• If you changed the resource limits, explain why it was needed.
• If the default configuration of Istio Operator has been changed, you performed a manual upgrade test to verify that the change can be rolled out correctly.
• Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
• Add release notes.

Attachments

• ADR
• part of: Support for egress gateway component #419

Follow-Up Issues

• ...