What would you like to be added:
Self-hosted Shoots, as proposed by GEP-28, run the Shoot control-plane components on the Shoot nodes instead of hosting them in a Seed cluster.
For this Shoot setup, the observability stack should provide the same data that a hosted Shoot provides. The backends should be deployed next to the control-plane components and data collection (e.g., ScrapeConfigs) be adjusted accordingly.
Self-hosted Shoots will typically be used as a Runtime or Seed cluster. The Shoot specific observability components should allow to deploy the Seed or Runtime specific observability component to the same cluster while redundancy should be avoided.
Why is this needed:
Provide logs and metrics to ensure reliable operation of self-hosted Shoot clusters.
What would you like to be added:
Self-hosted Shoots, as proposed by GEP-28, run the Shoot control-plane components on the Shoot nodes instead of hosting them in a Seed cluster.
For this Shoot setup, the observability stack should provide the same data that a hosted Shoot provides. The backends should be deployed next to the control-plane components and data collection (e.g., ScrapeConfigs) be adjusted accordingly.
Self-hosted Shoots will typically be used as a Runtime or Seed cluster. The Shoot specific observability components should allow to deploy the Seed or Runtime specific observability component to the same cluster while redundancy should be avoided.
Why is this needed:
Provide logs and metrics to ensure reliable operation of self-hosted Shoot clusters.