Kyma Modules State not updated when the remote cluster is unreachable

[nesmabadr]

Description

When the remote cluster is removed or unreachable, the kyma modules state in the Kyma.Status remain Ready, although it should be in an Error state.

There are several kymas which have this issue on DEV, for example: 926fb10a-925d-4c55-863d-a8a2da2ffb56.

Acceptance Criteria

• Status should be set to error if the cluster is not reachable
• Introduce E2E test for this scenario:

  lifecycle-manager/tests/e2e/deprovision_test.go

  Line 78 in 2342670

  It("When SKR Cluster is removed", func() {

Steps to reproduce

• Delete the remote cluster
• check the state of any enabled module in the Kyma.Status, it is in Ready state.

Environment Type

Managed

Environment Info

Kubernetes Version: x.y.z
Docker Version: x.y.z
modulectl Version: x.y.z
If used - k3d/k3s/minikube versions

Attachments

No response