Tobias Schuhmacher

I'm a bit scared to enable KIM to have access to all Hyperscaler accounts in Kyma. This would required per Hyperscaler dedicated credentials (read-only - best would be to have...

After alignment with @tmilos77 , we agreed to handover this EPIC to @kyma-project/phoenix team as their controller in KCP is already interacting with hyperscalers.

> Could the info also be taken from shoot.status.networking.egressCIDRs (from the gardener shoot object) and applied into the shoot? might be easier than taking it from the Hyperscaler. I've checked...

@ebensom : could we maybe also setup auditlog for all other regions? We would then directly configure them all together so that we are done from our side.

PR for this feature: https://github.com/kyma-project/control-plane/pull/3440

will be handled by KIM only.. closing this as it's duplicate of https://github.com/kyma-project/infrastructure-manager/issues/241

POC was successfully finished. We need also adjustments on ISTIO side to get dual-stack supported. @strekm : can you please provide the issue on your side and link it in...

Status update: * Implementation on KIM side completed (changes currently in review). Documentation outstanding. * As agreed, the Istio related changes be applied at a later time and customers start...

After a call with @ScheererJ we agreed on following options for the seed determining logic: 1. We change the visibility of the `determineSeed` function (from `determineSeed` to `DetermineSeed`) on the...