[Operational Awareness] Shoot Spec dumping: ensure the logic it is not blocking

[tobiscr]

Description

We have to agree how we proceed with the feature of dumping a shoot-spec to a storage (= dry-run mode for reconciling a RuntimeCR).

It turned out, that it could be useful for debugging purposes, but we also have to rethink the current implementation to make this feature more flexible and useful for operational analysis.

Requirements for this feature could be:

• Make final agreement if we still see a value in this feature for the future (do we have use-cases where it will be helpful for analyisis?
• It's possible to configure on the RuntimeCR level if it should run in Dry-Run mode (means, the Shoot-Spec will be dumped to a storage instead written to Gardener-Seed cluster)
• The action of dumping a shoot-spec is non-blocking for KIM (runs asynchronously and will -even in case of failures - never lead to blocking go-routines in KIM)

AC:

• TBC after triaging this issue

Reasons

Improve options for analysing KIM reconciliation-behaviour when KIM is running on a productively.

Attachments