Vedran Lerenc

@timuthy Will it be really `configMapName` or will inline priorities be also supported? BTW, in case you plan only for a config map name (less convenient than inline), please note...

> I don't think we will support inline priorities to not overload the Shoot resource. I guess this can grow quite large if you have many worker pools. @rfranzke Worker...

@dongyingbo: > I would like to make the configmap part of shoot yaml, so that gardener controller can create it in between control plane ready and system component deployment. You...

@rfranzke @tobschli Wow... that is a difficult question. First the easy answer: Yes, it is not necessary to even define a `configmap` for CA (as you know). CA will already...

@unmarshall called me (independently and by chance) and he is also in favour of abandoning the CA API/`configmap` and having the `priorities` right with the pools as @tobschli suggested. He...

@dongyingbo I cannot follow. Here some comments: - The CA is part of the control plane. Whether a configmap exists or not. - I still do not understand, why a...

> Check if the currently hard-coded values of 25GB/28GB could be computed based on the allocatable capacity of the seed nodes. Internally, we are exploring this, but the task is...

Out of curiosity: Isn't the title somewhat misleading? The dashboard will always require permissions to read and write (cloud provider) secrets, but in that case (different than viewers), it's done...

Same issue here. One can quickly profile it by running: `python -X importtime your_code_that_imports_litellm.py` Importing LiteLLM requires a lot of time and the larger it gets (the more it supports),...

I do not really understand the proposal/why you recommend it @epDHowwD. It also reads very complex, even complicated. Maybe, let's go back to what you want: Credentials rotation and being...