eskild

A more complete solution is needed. Closing this now.

Thanks for the update @rsignell-usgs! @costrouc I'm surprised that this was an issue for Rich. The `general` node group appeared to be in both subsets (just as the `worker` node...

I think you're encountering the same issue I did when I last attempted to update Azure to use OIDC: https://github.com/nebari-dev/nebari/issues/1694

The `nebari destroy` is working for GCP. Closing this issue.

We have documented the process in the FAQ section of the docs [here](https://www.nebari.dev/docs/faq#how-do-i-clean-up-or-delete-the-conda-store-pod-if-i-need-to).

@costrouc I believe this has been resolved but feel free to open this if you think this is still an issue.

Over the past few months, we have added a few tests that test the Nebari python dependencies. The integration tests now also test the cloud dependencies. Closing for now.

@costrouc do you have a sense of difficult (or feasible) this might be?

@trallard the associated [PR](https://github.com/nebari-dev/nebari/pull/1610) is still open but I just linked the two :)

So far I have tried (or researched) the following with no success: - UTM virtual machine - virtualbox virtual machine - last time I was reading about this, it wasn't...