Would you consider scaling back based on cyclical changes in carbon intensity as well?

[mrchrisadams]

Hi there.

Thanks for making this project - I wanted to ask about the roadmap for this project, and check I understand how this works.

kube-green currently works by "powering down" pods between certain times of day, right?

Are there aany other criteria in use at all? I ask we there is a project that might be relevant we worked on, called grid-intensity-go, specifically designed to support carbon aware cloud scheduling, and I figured before creating any issues or PRs to contribute to this project I might ask about the general direction of the project.

If it helps, this blog post here might help - we outlined a few approaches for greener scheduling of cloud compute using tools like Kubernetes and Nomad, and I'd be curious of any of these ideas might fit in the kube green roadmap in future.

https://www.thegreenwebfoundation.org/news/carbon-aware-scheduling-on-nomad-and-kubernetes

[davidebianchi]

Hi @mrchrisadams!

Yes, kube-green works exactly in this manner, at the moment it is the only criteria.

The grid-intensity-go seems an interesting project. With kube-green the main use case is to stop workload outside business hours, so I think it might be interesting to restart pods on region with lower carbon intensity in the specified day. But to do it, the cluster should be multi region. Did I understand correctly?

Anyhow, I think it could be an interesting new use case to handle also the batch workload based on the impact metrics. I think this could be well related to the kube-green use case.

[LappleApple]

@mrchrisadams Thoughts on what Davide's shared -- do you think contributing here could be an option?

@davidebianchi Thoughts on having a chat with Chris and team to brainstorm different options? If so, I could set that up.

[mrchrisadams]

hi Davide, Lauri,

I'm going to be travelling for the next week but it would indeed be good to compare notes on this. There's some earlier work that @rossf7, and myself did on a golang library for exposing some metrics you might use in scheduling decisions, and we initially looked at KEDA as a possible place to introduce this scaling previously. there may be some ideas there that are of use

kedacore/keda#3467

Otherwise though, I'd totally be up for chatting in April 👍

[LappleApple]

Hi @davidebianchi, can you please let us know your thoughts on a chat? Or would you rather Chris draft his ideas and post for async review and comment?

In related: I was going to go through your backlog of issues and make a spreadsheet to organize them, then review altogether so I can A) get a better sense of what folks are asking for B) identify themes that will be helpful in crafting a concise user survey; C) similar to B, but to create a questionnaire we could send out to current adopters. This data collection would be helpful for shaping the roadmap to help Chris and others understand the project goals better. LMK if you have any feedback or thoughts on the approach.