Application Connector - module CR has to move into WARNING state when failed to synchronise the runtime with Compass

[tobiscr]

Description:

The status of Application Connector Module does not reflect the state of connectivity with Compass services as stored in the CompassConnection CR.

Currently the module statusshows as "Ready" only when all module pods are healthy and Istio resources are available.

Details

We need to check periodically compassconnections.compass.kyma-project.io CR state and set the ACM module CR state as READY only if compassconnections state is Synchronized.

When compassconnection CR is in any of states below:

• Connected
• ConnectionFailed
• ConnectionMaintenanceFailed
• SynchronizationFailed
• ResourceApplicationFailed
• MetadataUpdateFailed

The Application Connector Module CR should be set to WARNING state

Impact:

Implementing this issue should enhance possibility to diagnose problems with the module and mitigate such problems with compass connectivity much faster than before.

More info:

1. Please check actual list of possible states of compassconnection with compass-runtime-agent source code
2. You can use synchronizationStatus field to set warning message for the user. Example:

  synchronizationStatus:
    error: 'Failed to fetch configuration: Failed to fetch Applications and Labels:
      graphql: Invalid data [reason=runtime does not exist]'