feat: add EnergyGradient scheduler plugin for EGS

[oerc-s]

Summary

Adds scheduler plugin that scores nodes based on energy gradients exposed via /egs/v1/gradient endpoints.

What is EGS?

EGS (Energy-Gradient Signaling) is a standard for exposing executable marginal energy capacity to autonomous systems.

Autonomous allocators select capacity via gradient. This plugin enables Kubernetes to participate in energy-aware allocation.

Plugin

• Name: EnergyGradient
• Type: Score plugin
• Annotation: egs.ear-standard.org/endpoint

Scoring

score = marginal_capacity_kw × (1 - cost_index) × (thermal_headroom_pct / 100)

Nodes with higher marginal capacity, lower cost, and higher thermal headroom receive higher scores.

Files

• pkg/energygradient/energygradient.go — Plugin implementation
• pkg/energygradient/README.md — Documentation

Reference

• EGS Standard: https://ear-standard.org
• EGS Exporter: https://github.com/oerc-s/egs-exporter

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[linux-foundation-easycla]

• ❌ The email address for the commit (32aaf81) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @oerc-s!

It looks like this is your first PR to kubernetes-sigs/scheduler-plugins 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/scheduler-plugins has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @oerc-s. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: oerc-s
Once this PR has been reviewed and has the lgtm label, please assign huang-wei for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-scheduler-plugins canceled.

Name	Link
🔨 Latest commit	32aaf81
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-scheduler-plugins/deploys/6973d1b9a7b55d0008262177

[ffromani]

/ok-to-test

[k8s-ci-robot]

@oerc-s: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-scheduler-plugins-unit-test-master	32aaf81	link	true	/test pull-scheduler-plugins-unit-test-master

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.