Create Application Connector module [EPIC]

[franpog859]

Description

Application Connector needs to be moved to the modular architecture according to this concept.

Reasons

Application Connector should be more independent so that it must be possible to install, upgrade and operate it separately without dependencies on other Kyma modules.

Acceptance criteria

Release 1.0.0:

• Application Connector module must have self-healing properties.
• Operator's configuration must be defined dedicated CRD
• Module must contain legacy Application Connector Components : Application Gateway and Connectivity Validator.

Release 1.1.0:

• Module must contain all Application Connector Components : Application Gateway, Connectivity Validator, and Compass Runtime Agent.

Prerequisites:

• Clean up Application Connector charts kyma#15915
• Clean up Istio usage in the Application Connector and Compass Runtime Agent charts to prepare for modulatisation kyma#16169
• Configurable Application Gateway kyma#15526 - Not needed for GA

Workplan:

• Prepare POC for Application Connector module kyma#15864
• Prepare pipeline for building, testing, linting
• App Connector Module - Implement reaction for a change of app-connector custom resource  #29

Until the end of September, Release MVP:

• App Connector Module - Prepare CRDs according to the new applicationconnector_types.go #18
• App Connector Module - Implement setting of correct status of app-connector CR when Istio is missing #24
• Prepare customer-facing documentation for Application Connector Module #6
• App Connector Module - Implement host name setup for Istio Gateway with Kyma cluster domain #23
• App Connector Module - Connect security tools to the module #7
• App Connector Module - Migrate testing pipelines from prow to Github Actions #31
• App Connector Module - Security Fixes for release 1.0.0 #64
• App Connector Module - Make the repository reuse compliant #34
• App Connector Module - Application Connector migration plan #21
• App Connector Module - Basic Kyma Dashboard UI #19
• App Connector Module - Integrate module template with lifecycle manager #36
• CR description of Application Connector #88

Release required tasks, until 25 October: Milestone 1.0.0

• Testing on stage completed
• 4 Golden signals agreed to be treated as monitoring dashboard
• App Connector Module - Troubleshooting guide #20
• Complete all microdelivery tasks
• Move application CRD from application-connector to compass-runtime-agent kyma#18312

Release hardening, until mid of November: Milestone 1.1.0

• Fix GH Actions to be required for merge #87
• App Connector Module - Add Runtime Agent [EPIC]  #48
• App Connector Module - Add Compass Runtime Agent to the module #53
• App Connector Module - Include Compass Runtime Agent into application-connector module #27
• App Connector Module - Migrate component tests from Kyma repo to the module #17
• Update the AC module documentation to the current state of the module #41

Consider to close as non-relevant:

• Make Application Connector module production ready (beta) kyma#17993
• App Connector Module - [Optional task] Ensure that Runtime Agent is enabled even if Istio is missing #40
• Application Connector module development on a "preview" plan with delivery process E2E kyma#17992

Additional information

• Related issues for delivery process E2E and making the module production ready for KEDA:
  • Keda module development on a "preview" plan with delivery process E2E kyma#16494
  • Make keda module production ready (beta) kyma#16550

[akgalwas]

For the time being Application Connector integration tests do not need to be modified. At some point we will move from Kyma repository. We will need to establish new pipelines and adjust the tests code if needed, however, it is not the top priority for now.
Additional question: should we test Operator along with Compass Connector components (Application Gateway, Connectivity Validator, and Compass Runtime Agent)? Or Operator and stuff it install should be tested separately?

[akgalwas]

We have three areas to test:

• Operator behaviour
• Application Gateway, Application Validator, and Compass Runtime Agent
• Compass Manager logic

We discussed the topic and agreed to use contract testing approach:

• Application Connector Module Operator will be tested separately with some mocked chart.
• Application Connector components will be tested separately and most functionality will be reused from existing tests (new pipeline will be needed)

[akgalwas]

Application Operator Module CRD must contain the following properties:

• domainName to be used in Istio Gateway, and Istio Virtual Service
• secret with TLS certificate to be used by Istio Gateway

Both values are optional so Operator must implement fallbacks:

• if secret is not provided, Certificate CR must be created
• if domainName is not provided, Gardener's domain must be used

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[tobiscr]

Done