Closed lieberlois closed 1 year ago
Just apply a config patch from the doc you referenced in Sidero Metal. Any Talos machine config change should be a config patch in Sidero/CAPI.
On what resource? 🤔 Would be great if this was added to the docs!
Like this?
apiVersion: controlplane.cluster.x-k8s.io/v1alpha3
kind: TalosControlPlane
metadata:
name: cluster-0-cp
namespace: default
spec:
controlPlaneConfig:
controlplane:
generateType: controlplane
talosVersion: v1.5.1
configPatches:
- op: replace
path: /cluster/allowSchedulingOnControlPlanes
value: true
infrastructureTemplate:
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha3
kind: MetalMachineTemplate
name: cluster-0-cp
replicas: 1
version: v1.28.1
yes, controlplane makes sense
So that configPatch should work?
configPatches:
- op: replace
path: /cluster/allowSchedulingOnControlPlanes
value: true
you can test config patches with talosctl gen config
if you want to test it before applying offline
By default, sidero provisioned control plane nodes will have the NoSchedule taint. In the documentation, I have found nothing to reconfigure that. Its possible to configure that for Talos (https://www.talos.dev/v1.5/talos-guides/howto/workers-on-controlplane/) but I havent found anything regarding the sidero clusterapi provider.