Tobias Schuhmacher

Feedback from stakeholders: @ebensom : * from operational side, we should not expose all worker-pool configurations of the Shoot spec (e.g. each worker can have different linux-image versions which can...

**Next steps / Action items:** 1. @PK85 + @ebensom : decide on the configruation options we are exposing for customers and track it in this issue 2. @PK85 : Inform...

Hi @ChristophRothmeier , thanks for your request. The multiple worker pool feature is currently in implementation and will be rolled out till end of this year. The list of supported...

Hi @ChristophRothmeier -we are currently working on the worker-pool implementation. We are not sure if we can support scaling to 0 nodes as it seems that Gardener expects that the...

@ChristophRothmeier : please excuse the delayed reply. I also want to apologise that customised worker pools are still not consumable on production. We are currently integrating and testing the new...

Hi @ingentismg, thanks for reaching out! As indicator for the default worker-pools, I can confirm that the usage of the label `worker.gardener.cloud/pool: cpu-worker-0` is the best option. This label is...

Hi @ingentismg , UR welcome. We discussed today the current situation in our team an we agreed to introduce a dedicated label for the Kyma worker pool and customer owned...

> Thanks for the confirmation on the default pool name [@tobiscr](https://github.com/tobiscr)! We will proceed to implement a nodeSelector targeting `cpu-worker-0` for anything that should not run in another pool. Many...

Update documentation to cover node affinity / antiAffinity for assigning workload to worker-pools: https://github.com/kyma-project/infrastructure-manager/issues/709 Closing this EPIC as rollout is completed. Enhancement and follow-up actions are managed in separate issues.

@pbochynski - is this feature still required? Maybe worth to check our options again. I could imagine, if we can get the public IP somehow, we could cover this part...