search

k3s-io / k3s

Lightweight Kubernetes
https://k3s.io
Apache License 2.0
26.96k stars 2.27k forks source link

Reducing K3s Org Equinix usage #9956

Open jeefy opened 2 months ago

jeefy commented 2 months ago

Hello! Friendly neighborhood CNCF person here.

K3s is currently using a significant amount of resources in Equinix. As they're bare metal instances, turning them off still leaves a reservation and burns unnecessary carbon so-to-speak.

We tried reaching out via the original thread here: https://github.com/cncf/cluster/issues/148 and we've attempted to slack numerous folks, and gotten radio silence. :)

PS this is all related to https://contribute.cncf.io/resources/newsletters/2024-02-21-projectnewsletter/#equinix-updates and the resource usage policy linked further below. :) Thanks!

brandond commented 2 months ago

Thanks for opening an issue! I will reach out to our infra folks about releasing the previous generation of CI runners.

cwayne18 commented 2 months ago

My apoloigies for missing this, we're getting right on it!

vielmetti commented 2 months ago

@cwayne18 Looking forward to hearing your progress on this.

idvoretskyi commented 2 months ago

/cc @idvoretskyi

jeefy commented 2 months ago

Heya! Quickly checking in here :) It looks like you're moving towards some sort of gitops-controlled workflow (yay!)

Small reminder that machines in Equinix are bare metal and therefore even though they're powered off, they're still "Reserved" and go against our donation. When you're done and ready to move towards your new machines/setup, please delete the old ones.

Thanks! If you have any other questions or are blocked on anything, please reach out to @vielmetti or myself

brandond commented 2 months ago

I've poked our infra team again to ask them to take the final steps to release these hosts. I think we were under the impression that this was going to occur on the 18th of last month, thanks for the reminder to check in on that.

github-actions[bot] commented 2 weeks ago

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 45 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

idvoretskyi commented 2 weeks ago

Anything else should be completed here?