Add blog post on AKS Configurable Scheduler Profiles

[colinmixonn]

This blog post introduces AKS Configurable Scheduler Profiles, highlighting their benefits for optimizing resource utilization and improving scheduling strategies for web-distributed and AI workloads. It covers configuration examples for GPU utilization, pod distribution across topology domains, and memory-optimized scheduling.

[Copilot]

Pull request overview

This pull request adds a new blog post announcing the preview of AKS Configurable Scheduler Profiles, a feature that enables fine-grained control over pod scheduling strategies to optimize resource utilization and improve workload performance.

Key Changes

• Introduces a new "scheduler" tag to categorize blog posts related to pod placement and scheduling optimization
• Adds comprehensive blog post covering three main scheduling use cases: GPU bin-packing for AI workloads, pod distribution across topology domains for resilience, and memory-optimized scheduling with PVC-aware placement
• Provides YAML configuration examples and best practices for implementing custom scheduler profiles

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 20 comments.

File	Description
website/blog/tags.yml	Adds new "scheduler" tag for categorizing posts about pod placement and scheduling techniques
website/blog/2025-12-16-aks-config-scheduler-profiles-preview/index.md	New blog post introducing AKS Configurable Scheduler Profiles with configuration examples for GPU utilization, topology distribution, and memory-optimized scheduling

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated 1 comment.

[Copilot]

This example uses metadata.name: upstream. If readers apply multiple examples, they'll overwrite the same SchedulerConfiguration object. Use a profile-specific resource name (or call out that the name must be unique per cluster/namespace).

Suggested change

	name: upstream
	name: gpu-node-binpacking-scheduler-config

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated 1 comment.

[Copilot]

This says there are "three different scheduler profiles," but only two examples are listed. Either add the third example/section or update the wording to match the actual content.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated 3 comments.

[Copilot]

This example also uses metadata.name: upstream, which would conflict with the earlier example’s resource name. Please use a unique name here as well (or clarify that the earlier resource should be replaced).

[Copilot]

The reference label [scheduling-framework/#interfaces] includes / and #, which can be brittle across Markdown processors. Consider renaming the reference label to a simpler identifier (for example, scheduling-framework-interfaces) while keeping the same URL target.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 6 changed files in this pull request and generated 1 comment.

[Copilot]

This example uses metadata.name: upstream, and the CPU example later uses the same name. If readers apply both, they will conflict/overwrite. Consider giving each example a unique metadata.name to avoid copy/paste issues.

Suggested change

	name: upstream
	name: gpu-node-binpacking-scheduler

[Copilot]

Pull request overview

Copilot reviewed 2 out of 6 changed files in this pull request and generated 2 comments.

[Copilot]

The GPU example’s NodeResourcesFit args omits the typed wrapper (apiVersion/kind: NodeResourcesFitArgs) that you include in the CPU example. For documentation copy/paste reliability, keep both examples consistent with the kube-scheduler config schema (add apiVersion/kind in the first example as well) to avoid readers hitting validation/parsing errors depending on tooling.

Suggested change

	args:
	args:
	apiVersion: kubescheduler.config.k8s.io/v1
	kind: NodeResourcesFitArgs

[Copilot]

FAQ item #1 is a question without an answer. Either add an explicit answer (even if it’s a short guidance + link) or remove the question to avoid confusing readers.

Suggested change

1. How does this interact with autoscalers such as Node Auto Provisioning (NAP), Cluster Autoscaler (CAS), and Vertical Pod Autoscaler (VPA)?

1. How does this interact with autoscalers such as Node Auto Provisioning (NAP), Cluster Autoscaler (CAS), and Vertical Pod Autoscaler (VPA)? Configurable Scheduler Profiles control how pods are placed on existing nodes, while autoscalers still decide when to add, remove, or resize nodes based on resource demand. You should validate new profiles with your current NAP, CAS, and VPA settings in a test cluster to ensure they work together as expected before rolling them out to production.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 6 changed files in this pull request and generated no new comments.