# A patch applied on top of the controlplane.yaml that `talosctl gen config`
# produces (see talos/README.md and docs/02-talos-bootstrap.md for the full
# command). Talos's generated defaults assume a multi-node cluster where
# control-plane nodes only run the Kubernetes control plane itself (API
# server, scheduler, etcd, etc.) and never your actual workloads. For a
# single-node learning cluster, that would mean nothing can ever be
# scheduled — there's no other node to run it on.
#
# This one field undoes that restriction, letting the single node be both
# the control plane AND a worker.
#
# >> Ask Claude: "why does Kubernetes normally keep workloads off control
#    plane nodes?" if you want the reasoning before you turn it off.
cluster:
  allowSchedulingOnControlPlanes: true