Add CentOS Stream 10 Kubernetes v1.34.7 DHCP image for PowerVS

[aman4433]

What this PR does / why we need it:
Adds the CentOS Stream 10 Kubernetes v1.34.7 DHCP-enabled PowerVS image
to the machine image documentation and updates the infrastructure-creation
cluster example to use the new DHCP image artifact.

The image was built using image-builder with a custom DHCP-enabled base OVA
and validated using the PowerVS infrastructure-creation workflow.

Which issue(s) this PR fixes:
part of #2764

Special notes for your reviewer:
/area provider/ibmcloud

Please confirm that if this PR changes any image versions, then that's the
sole change this PR makes.

Validation:

• Built DHCP-enabled CentOS Stream 10 image using image-builder
• Uploaded image to power-oss-bucket as capibm-powervs-centos-streams10-1-34-7-dhcp.ova.gz
• Validated cluster creation using cluster-template-powervs-create-infra.yaml
• VM successfully obtained a DHCP lease and completed Kubernetes provisioning

Release note:
Add CentOS Stream 10 Kubernetes v1.34.7 DHCP image for PowerVS infrastructure-creation deployments

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!

Name	Link
🔨 Latest commit	07a9c2c
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-ibmcloud/deploys/6a21305b9fca0900088ed49f
😎 Deploy Preview	https://deploy-preview-2791.cluster-api-ibmcloud.sigs.k8s.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aman4433
Once this PR has been reviewed and has the lgtm label, please assign prajyot-parab for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Amulyam24]

@aman4433, can you please share the output of cluster deployment?

[aman4433]

Hi @Amulyam24, The cluster deployment completed successfully using the CentOS Stream 10 Kubernetes v1.34.7 DHCP image added by this PR.

Validation environment:

• CAPIBM main: 7dd563b10
• CAPI main: 0a0807d4d
• Template: cluster-template-powervs-create-infra.yaml
• PowerVS zone: osa21

The image used by the deployment is the image added in this PR:

$ kubectl get ibmpowervsimage capi-cluster-image -o yaml

spec:
  bucket: power-oss-bucket
  object: capibm-powervs-centos-streams10-1-34-7-dhcp.ova.gz
  region: us-south
  storageType: tier1
  workspace:
    name: capi-cluster-workspace
status:
  conditions:
  - reason: Ready
    status: "True"
    type: Ready
  imageID: c8e31c9a-3f53-4102-b2a2-7ed3f8ed1fd6
  imageState: active
  ready: true

Cluster infrastructure:

$ kubectl get ibmpowervscluster capi-cluster -o yaml

spec:
  network:
    provision:
      dhcpServer:
        name: capi-cluster
    type: Provision
  zone: osa21
status:
  conditions:
  - reason: Ready
    status: "True"
    type: Ready
  - reason: Ready
    status: "True"
    type: NetworkReady
  initialization:
    provisioned: true
  network:
    dhcpServer:
      id: cad72a71-702b-45d0-abd7-c94a560fe826
    id: 345b139a-ae45-4b83-a13d-c8eeac2afec7
    name: DHCPSERVERcapi-cluster_Private

Machine deployment:

$ kubectl get machines

NAME                               CLUSTER        NODE NAME                          FAILURE DOMAIN   READY   AVAILABLE   UP-TO-DATE   PHASE     AGE   VERSION
capi-cluster-control-plane-6n9vf   capi-cluster   capi-cluster-control-plane-6n9vf                    False   False       True         Running   23m   v1.34.7

$ kubectl get ibmpowervsmachine capi-cluster-control-plane-6n9vf -o yaml

spec:
  imageRef:
    name: capi-cluster-image
  providerID: ibmpowervs://osa/osa21/d31cbf0e-6394-4cb2-b5f1-21ed766396eb/69e5118d-a18f-43a5-9bf2-869df26f8d19
  sshKey: capi-key
  systemType: s922
status:
  addresses:
  - address: 192.168.0.10
    type: InternalIP
  conditions:
  - reason: Ready
    status: "True"
    type: Ready
  - reason: InstanceReady
    status: "True"
    type: InstanceReady
  health: OK
  initialization:
    provisioned: true
  instanceID: 69e5118d-a18f-43a5-9bf2-869df26f8d19
  instanceState: ACTIVE

The PowerVS image was imported successfully and reached imageState: active / ready: true. The IBMPowerVSMachine references that image, the VM booted successfully, acquired the DHCP address 192.168.0.10, and the CAPI Machine reached Running with the nodeRef and providerID populated.

For completeness, the READY=False / AVAILABLE=False shown in the Machine output is due to the workload node reporting NetworkPluginNotReady:

$ clusterctl describe cluster capi-cluster

NAME                                                             REPLICAS  AVAILABLE  READY  UP TO DATE  STATUS           REASON     SINCE  MESSAGE
Cluster/capi-cluster                                             1/1       0          0      1           Available: True  Available  32m
├─ClusterInfrastructure - IBMPowerVSCluster/capi-cluster                                                 Ready: True      Ready      42m
└─ControlPlane - KubeadmControlPlane/capi-cluster-control-plane  1/1       0          0      1
  └─Machine/capi-cluster-control-plane-6n9vf                     1         0          0      1           Ready: False     NotReady   39m    * NodeHealthy:
                                                                                                                                              * Node.Ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
                                                                                                                                                message:Network plugin returns error: cni plugin not initialized

No CNI addon was deployed as part of this create-infra validation flow.

Validation passed successfully.