Przemyslaw Golicz

Project design: - Kyma cluster installed in k3d mode - AppConnectivityValidator exists in kyma-system namespace - Deployed TestPod, and HttpBin service in separate testing namespace - AppConnectivityValidator patched to proxy...

PR with new test - https://github.com/kyma-project/kyma/pull/14912

As @mfaizanse investigated It seems like issue with registering Kyma with compass: ([logs](https://storage.googleapis.com/kyma-prow-logs/pr-logs/pull/kyma-project_kyma/15125/pre-main-kyma-integration-k3d-central-app-connectivity-compass/1560143558697029632/build-log.txt)) 1) Kyma with Compass test Register Kyma instance in Compass: Error: Error when updating label definition with...

Closing as we migrate to new module architecture. We might want to include this feature into app-connector-module

@pbochynski We **use** semantic versioning for application-connector-module. Version 1.0.3 is available in both fast and regular channel

Added task to configure following cluster parameters with Provisioner: ``` kubernetes: clusterAutoscaler: scaleDownDelayAfterAdd: scaleDownUnneededTime: ``` https://github.tools.sap/kyma/backlog/issues/4253

There is still a dependency to `istio-system` namespace. We must address it to avoid pod crashing without the namespace.

/test all

@tobiscr I think we should close this. This code is being gradually removed (. https://github.com/kyma-project/control-plane/pull/3438/files) and soon will be fully replaced with new `infrastructure-manager` service

Quote from Slack thread where we analysed the code: `Basically there is nothing wrong with the code, it’s just for many runtimes the VNet CIDR was expanded during the HA...