k3s icon indicating copy to clipboard operation
k3s copied to clipboard

Published 20 hours ago • verified publisher icon k3s-io

Reducing K3s Org Equinix usage

Open jeefy opened this issue 1 year ago • 8 comments
trafficstars

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.

  • Can you work with @vielmetti and I on optimizing your usage?
  • Do you need all those nodes sitting idle?
  • Is there a way to spin up nodes as needed?
  • What's preventing you from using GitHub actions?

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!

jeefy avatar Apr 16 '24 20:04 jeefy

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

brandond avatar Apr 16 '24 20:04 brandond

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

cwayne18 avatar Apr 17 '24 15:04 cwayne18

@cwayne18 Looking forward to hearing your progress on this.

vielmetti avatar Apr 23 '24 14:04 vielmetti

/cc @idvoretskyi

idvoretskyi avatar Apr 25 '24 10:04 idvoretskyi

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

jeefy avatar Apr 30 '24 20:04 jeefy

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.

brandond avatar May 01 '24 23:05 brandond

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.

github-actions[bot] avatar Jun 16 '24 20:06 github-actions[bot]

Anything else should be completed here?

idvoretskyi avatar Jun 18 '24 09:06 idvoretskyi

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.

github-actions[bot] avatar Aug 02 '24 20:08 github-actions[bot]

Closing this out is fine; if something comes up in the future that needs further attention there will be a new issue + a link back to this one.

vielmetti avatar Aug 16 '24 20:08 vielmetti