kops metal cluster doesn't automatically install bootstrap addons (kops-controller, CNI, etc)

[apeabody]

/kind bug

1. What kops version are you running? The command kops version, will display
this information.

Client version: 1.33.0 (git-v1.33.0

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

Client Version: v1.32.4-dispatcher
Kustomize Version: v5.5.0
Server Version: v1.32.4

3. What cloud provider are you using?

Metal

4. What commands did you run? What is the simplest way to reproduce this issue?

kops create cluster --cloud=metal metal.k8s.local --zones main --networking calico
kops edit cluster metal.k8s.local  --set spec.api.publicName=
kops update cluster metal.k8s.local --yes --admin
kops toolbox enroll --cluster metal.k8s.local --instance-group control-plane-main --v=2

5. What happened after the commands executed?

The cluster was created and the control plane node enrolled with etcd and kube-apiserver, however it did not automatically deploy the bootstrap addons.

This was used to force their deployment:
kops toolbox addons apply gs://{}/metal.k8s.local/addons/bootstrap-channel.yaml --yes

6. What did you expect to happen?

I expected the cluster to be bootstrapped with all the resources listed by kops create cluster.

7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?