Closed JacobValdemar closed 5 months ago
Open question: Where exactly to integrate this into Karpenter?
Worth exploring: https://github.com/aws/karpenter-core/issues/693
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What was the outcome on this?
Abstract ("TLDR")
This RFC proposes the addition of an "Environmental Sustainability Mode" to Karpenter. When Environmental Sustainability Mode is enabled, Karpenter optimize scaling decisions based on carbon emissions. This feature will help organizations make more environmentally responsible choices when it comes to provisioning and scaling their Kubernetes clusters.
Edit (22-04-2024): I finished my master's thesis where I have implemented this. Check it out here: https://github.com/JacobValdemar/carbon-efficient-karpenter-thesis
Motivation
Climate Change is important. As the global community continues to focus on reducing carbon emissions and environmental impact, it is crucial for technology projects to align with these objectives. Data centers, where Kubernetes clusters typically run, are significant contributors to carbon emissions. Optimizing node provisioning to minimize the carbon footprint of Kubernetes clusters is becoming increasingly important.
By implementing an Environmental Sustainability Mode in Karpenter, we can empower Kubernetes Administrators to make environmentally conscious decisions when managing their Kubernetes clusters.
Proposal
When this mode is enabled, Karpenter may minimize the following two metrics (independently):
Usage
It could be enabled like this:
or like this:
I don't know what is the best solution. Any input on this?
Default?
I have been made aware, that many seem to back Karpenter's move to CNCF (https://github.com/kubernetes/org/issues/4258) based on opportunities within sustainability. That could be an argument for making Karpenter sustainability-first and enabling this feature by default. In that case, it could be possible that this feature is not developed as an "optional mode", but more as an evolution of Karpenter. We would of course need to discuss the implications of that before we pursue that path. However, for now, I will assume that the feature is developed as a non-default mode.
Implementation
I will be doing the implementation as part of my master's thesis.
Possible methods:
Open question: Where exactly to integrate this into Karpenter?
Naming
I am unsure about what this mode should be called. Here are the options that are currently on the table:
Resources