Open rfranzke opened 1 year ago
If you discuss switching to a custom resource instead of Secret
s please consider the problems tackled in https://github.com/gardener/gardener/pull/7959 and https://github.com/gardener/gardener/pull/8116, i.e. that right now there is no reliable mechanism to check if the latest version of the resources is applied or not.
The Gardener project currently lacks enough active contributors to adequately respond to all issues. This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
/lifecycle stale
The Gardener project currently lacks enough active contributors to adequately respond to all issues. This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
/lifecycle rotten
/remove-lifecycle rotten
The Gardener project currently lacks enough active contributors to adequately respond to all issues. This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
/lifecycle stale
/area dev-productivity /kind enhancement
For historic reasons, shoot control plane components are applied directly via the client (example) while system components are deployed via
ManagedResource
s (example).Using
ManagedResource
s has multiple benefits, most prominentlyHence, we should think about transitioning also to
ManagedResource
s for the shoot control plane components.Before we start, we should evaluate:
Secret
s for the resources part ofManagedResource
s?