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

Alive? #119

Open
pschulten opened this issue Aug 28, 2021 · 7 comments
Open

Alive? #119

pschulten opened this issue Aug 28, 2021 · 7 comments

Comments

@pschulten
Copy link

This repo seems to be abandoned

Are there any good alternatives?

Very sorry, if I'm mistaken :(

@shelby-moore
Copy link

Bump, I'd like to contribute some fixes but only looks like those with write access can merge changes.

@rbjorklin
Copy link

@negz you're the top contributor to this repo, do you know if it is still being maintained?

@genehand
Copy link

genehand commented Mar 4, 2022

We switched over to the descheduler that includes some additional policies & balancing options. Been working well 👍

@rbjorklin
Copy link

rbjorklin commented Mar 4, 2022

descheduler can't drain based on custom node conditions though.
The required feature might land in NPD.

@negz
Copy link
Collaborator

negz commented Mar 5, 2022

Hi folks! I'm the original author of Draino, but I no longer maintain it as of when I left @planetlabs a little over 3 years ago. I no longer have maintainer access to this repository. @jacobstr took over after I left, and while I believe he's still at @planetlabs I don't think he's maintaining Draino anymore.

I don't personally have time to maintain it as I'm busy working on @crossplane, and I suspect there may be issues adding non @planetlabs maintainers to this repo. If someone is interested in maintaining Draino you definitely have my blessing to fork it in a more open org. :)

@rbjorklin
Copy link

Oh, it looks like DataDog is maintaining their own fork of this: https://github.com/DataDog/draino

@aantn
Copy link

aantn commented May 29, 2022

Hi @negz,
I'm the maintainer of @robusta-dev and we work fulltime on an open source for auto-remediation in kubernetes clusters. We don't have a node-drain automation right now, but based on the interest here, it seems like we should.

Is that correct?

We're https://github.com/robusta-dev/robusta if it's not obvious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants