Should deploying with changed taints or environment profiles update the cluster?

[satra]

I'm noticing that changing certain aspects of the config don't have any effect on the deployment:

• changing node_group taints doesn't alter launch configuration templates
• chaging environment package lists don't update the corresponding conda-store build

in both cases the original config settings are maintained. is this expected?

• deploying on aws
• sequence of render + deploy

[viniciusdc]

Hey @satra, thanks for raising those points. I am curious about those items.

Changing node_group taints doesn't alter launch configuration templates

Can you provide an example of such a change? I am particularly curious about this one.

Changing environment package lists don't update the corresponding conda-store build

When the environments are updated, they should trigger a new environment build in Celery (Queue), which will be picked up and updated. You should see a new build appear. If that's not working, then there is a bug.

We will update the documents, as there is an ongoing discussion to remove or decommission that section from the YAML. Regarding the rendering process, when you perform a deploy, it is done under the hood.

[marcelovilla]

When the environments are updated, they should trigger a new environment build in Celery (Queue), which will be picked up and updated. You should see a new build appear. If that's not working, then there is a bug.

That is true for environments changed via the GUI (i.e. the /conda-store endpoint), but as far as I am aware, changes to environments declared in the nebari-config.yaml file won't trigger any updates as those are only meant to be built during the first deployment.