Attaching listerner to Loadbalancer failed.

[Karthik-K-N]

/kind bug /area provider/ibmcloud

What steps did you take and what happened: [A clear and concise description of what the bug is.]

spec:
  loadBalancers:
  - name: capi-powervs-karthik-loadbalancer
  - name: capi-powervs-karthik-lb-clusterNetwork

Error

Invalid json payload provided: Message: Validation Failure for field: listeners[0].default_pool.name Code: validation_failed_pattern TargetName: listeners[0].default_pool.name TargetType: field TargetValue: capi-powervs-karthik-lb-clusterNetwork-pool-6443:: Message: Validation Failure for field: name Code: validation_failed_pattern TargetName: name TargetType: field TargetValue: capi-powervs-karthik-lb-clusterNetwork:: Message: Validation Failure for field: pools[0].name Code: validation_failed_pattern TargetName: pools[0].name TargetType: field TargetValue: capi-powervs-karthik-lb-clusterNetwork-pool-6443::

What did you expect to happen:

Anything else you would like to add: It would be great if we can evaluate all the resources like workspace, DHCP, Transit gateway in spec against their specifications against the IBMCloud api doc, For example

TranistGateway: https://cloud.ibm.com/apidocs/transit-gateway#create-transit-gateway

Environment:

• Cluster-api version:
• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[Karthik-K-N]

On initial look it seems like the camelCase format of name capi-powervs-karthik-lb-clusterNetwork-pool-6443 causing the issue.

Action items

1. Explore on naming format for vpc, vpcsubnet, loadbalancer, listerner.
2. Update api to add kubebuilder tag
3. May be consider converting it to smaller case before creating resources.

[Shilpa-Gokul]

/assign @Shilpa-Gokul