Xin Ruan

Take into consider this issue: https://github.com/kyma-incubator/reconciler/issues/1042

The shoot which has vpn error ``` error dialing backend: proxy error from vpn-seed-server:9443 while dialing 10.250.0.2:10250, code 503: 503 Service Unavailable ``` https://dashboard.garden.live.k8s.ondemand.com/namespace/garden-kyma-prow/shoots/grd6fhsbu/ Related logs: https://status.build.kyma-project.io/log?container=test&id=1589633053381103616&job=ruanxin_test_of_prowjob_pre-main-control-plane-reconciler-upgra

fix in PR: https://github.com/kyma-project/test-infra/pull/6348

vpn connection issue is not the root cause.

For Validation in Submission Pipeline: https://github.tools.sap/kyma/test-infra/issues/453

We as jellyfish have doubt about using the lifecycle-manager to label the `kube-system` namespace. The `kube-system` namespace is special because it contains Kubernetes system components, none of which are reconciled...

# Open questions 1. Support user preconfig extension during kyma provsion or not 1. How to monitor extension status 2. SLA for those extensions

## Vote for extension enablement: Based on our discussions, we’ve identified the following options for enabling Gardener extensions in Kyma. Please review and share your opinion: 1. Enabled by Default...

@pbochynski To answer you questions: > Can we treat falco extension in the same way as registry cache? Yes, we can, and in fact would be simpler. I clarified with...

Regarding the statement "Customers should explicitly opt-in to use such Gardener extensions", I clarified this with @tobiscr. Ideally, the concern about existing SKRs not being fully backward-compatible with the Gardener...