Vinicius D. Cerutti

The RFD above has been accepted, and the work referenced in this issue and in the RFD itself has been broken down in the following issues: - #2308 - #2432...

I am reopening this issue, as we needed to rollback the upgrades due to a BUG within the conda-store recent UI updates

@aktech this is not required anymore correct?

> I'm also curious what issues you've seen from this. It seems like it shouldn't cause a problem to use different provider versions in different stages. I haven't noted any...

Hi @smokestacklightnin , thanks for the feedback and the ideas above. I have overall points at the end, but first, I wanted to provide some context regarding the templates and...

Thanks for the comprehensive overview and the POCs, @smokestacklightnin. I’m leaning towards **Path 1: Not using Renovate**. The main goal here is to ensure all providers use the same version...

Hi @Adam-D-Lewis it seems that during your tests you found this is really troublesome to handle using the current available capabilities of the yaml tools, is that right?

Just a quick update on this. I've finished refactoring the parser to `spawner.py` to handle the new role scopes for the mounts (I used the sample response shared [here](https://github.com/nebari-dev/nebari/pull/2447#pullrequestreview-2054802217)) and...

For handling the items below, just adding as ref., we used to have a test in a private repo that handled that, it might be worth checking that: ```yaml Redeploy...

> While I don't think this is the issue, it occurs to me that the other nodes might be scaling up b/c we have more pods than cpu/memory on the...