https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/workload-aware-scheduling/Recent content in WG Workload-aware Scheduling on Kubernetes ContributorsHugoenhttps://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/workload-aware-scheduling/charter/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/wg/workload-aware-scheduling/charter/<h1 id="wg-workload-aware-scheduling-charter">WG Workload-aware Scheduling Charter</h1> <p>This charter adheres to the conventions described in the <a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md" target="_blank" rel="noopener">Kubernetes Charter README</a> and uses the Roles and Organization Management outlined in <a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md" target="_blank" rel="noopener">wg-governance</a> .</p> <h2 id="scope">Scope</h2> <p>Native support for workload-aware and topology-aware scheduling in core Kubernetes. Today, these concerns are spread across multiple SIGs and ecosystem projects, and the lack of a shared model for expressing workload-level requirements and infrastructure topology makes it difficult to coordinate placement decisions consistently and efficiently.</p>