Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENH - Update node pool usage for ClearML #1281

Closed
Tracked by #1309
viniciusdc opened this issue May 13, 2022 · 1 comment
Closed
Tracked by #1309

ENH - Update node pool usage for ClearML #1281

viniciusdc opened this issue May 13, 2022 · 1 comment

Comments

@viniciusdc
Copy link
Contributor

This was first spotted by @leej3 in #984, where he identified that some of ClearML inner resources didn't have a specific node selector key assigned to them, leading to some of those having weird behaviors when scaling for node usage, e.g. they could be deployed at wherever node available in the referred namespace disregarding the correct resource tags (in this case ClearML).

@trallard trallard changed the title [Enh] Update node pool usage for ClearML ENH - Update node pool usage for ClearML Jan 12, 2023
@trallard trallard changed the title [Enh] Update node pool usage for ClearML ENH - Update node pool usage for ClearML Jan 12, 2023
@iameskild iameskild added this to the The Release After Next milestone Oct 16, 2023
@iameskild iameskild removed this from the 2023.11.1 milestone Nov 8, 2023
@aktech
Copy link
Member

aktech commented Feb 8, 2024

We dropped support for ClearML

@dcmcand dcmcand closed this as completed Feb 8, 2024
@github-project-automation github-project-automation bot moved this from New 🚦 to Done 💪🏾 in 🪴 Nebari Project Management Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants