Mastering Kubernetes - Second Edition

Deploying the custom scheduler

Now that the scheduler image is built and available in the registry, we need to create a Kubernetes deployment for it. The scheduler is, of course, critical, so we can use Kubernetes itself to ensure that it is always running. The following YAML file defines a deployment with a single replica and a few other bells and whistles, such as liveness and readiness probes:

apiVersion: apps/v1 kind: Deployment metadata: labels: component: scheduler tier: control-plane name: custom-scheduler namespace: kube-system spec: replicas: 1 template: metadata: labels: component: scheduler tier: control-plane version: second spec: containers: - command: - /usr/local/bin/kube-scheduler - --address=0.0.0.0 - --leader-elect=false ...