Satellite Daemon Set for new nodes?

[panoukos41]

I have a Talos linux cluster and I recently added a new node and configured my resource group with a placement count of 2. I noticed that the second node is offline and that no satellite has been configured to run there. Is this normal? How do I get my new node to have the satellite?

Below are my configurations and a list of daemon sets as shown in freelnes.

apiVersion: piraeus.io/v1
kind: LinstorCluster
metadata:
  name: linstorcluster

apiVersion: piraeus.io/v1
kind: LinstorSatelliteConfiguration
metadata:
  name: storage-pool
spec:
  storagePools:
  - name: file-pool
    fileThinPool:
      directory: /var/lib/linstor/file-pool

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: file-storage
provisioner: linstor.csi.linbit.com
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer
parameters:
  linstor.csi.linbit.com/storagePool: file-pool
  linstor.csi.linbit.com/placementCount: "2"

I also noticed the satelite.c01 has this affinity which leads me to believe that a new satelite.c02 with the same affinity should be created.

nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchFields:
      - key: metadata.name
        operator: In
        values:
        - c01

[panoukos41]

Okay I removed the taint of node-role.kubernetes.io/control-plane:NoSchedule but after a restart Talos must have added it back. So I have been searching so much for something so simple. Here is a link to the documentation which explains how to do it in the machine configuration.