Bug 1994142

[QA Summary]

[Parameters]

~~~
$ export TAGS=ibmcloud
$ export IC_API_KEY='<apiKey>'
~~~

[Version]

~~~
$ ./openshift-install-local version
./openshift-install-local unreleased-master-4997-g422e17192462f2b5d5572d8600096949d3c14634
built from commit 422e17192462f2b5d5572d8600096949d3c14634
release image registry.ci.openshift.org/origin/release:4.8
release architecture amd64

$ git --no-pager log --oneline --first-parent origin/master -3
422e17192 (HEAD -> master, upstream/master, origin/master, origin/HEAD) Merge pull request #5158 from stevekuznetsov/skuznets/footprint-gcp
a94ceeaaf Merge pull request #5152 from hasueki/ibm-cloud-config
379f05b0e Merge pull request #5197 from shiftstack/openstack_quota
~~~

[Results]

~~~
$ ./openshift-install-local explain installconfig.platform.ibmcloud
KIND:     InstallConfig
VERSION:  v1

RESOURCE: <object>
  IBMCloud is the configuration used when installing on IBM Cloud.

FIELDS:
    defaultMachinePlatform <object>
      DefaultMachinePlatform is the default configuration used when installing on IBM Cloud for machine pools which do not define their own platform configuration.

    region <string> -required-
      Region specifies the IBM Cloud region where the cluster will be created.

    resourceGroupName <string>
      ResourceGroupName is the name of an already existing resource group where the cluster should be installed. This resource group should only be used for this specific cluster and the cluster components will assume ownership of all resources in the resource group. Destroying the cluster using installer will delete this resource group. 
 This resource group must be empty with no other resources when trying to use it for creating a cluster. If empty, a new resource group will be created for the cluster.

    subnets <[]string>
      Subnets is a list of existing subnet IDs. Leave unset and the installer will create new subnets in the VPC network on your behalf.

    vpc <string>
      VPC is the ID of an existing VPC network. Leave unset and the installer will create a new VPC network on your behalf.

    vpcResourceGroupName <string>
      VPCResourceGroupName specifies the resource group containing an existing VPC. This must be defined if `VPC` is defined.

$ ./openshift-install-local create install-config --dir test22/
? SSH Public Key /home/pamoedo/.ssh/id_rsa_ibm.pub
? Platform ibmcloud
? Resource Group pamoedom-rg (9c9c22f31a8141aab51b772ceabac0b2)
? Region eu-de
? Base Domain ibmcloud.qe.devcluster.openshift.com (openshift-qe-cis)
? Cluster Name pamoedo-test
? Pull Secret [? for help] *************************************************************************************************************************************************************************************************************************
[...]
INFO Install-Config created in: test22

$ cat test22/install-config.yaml 
apiVersion: v1
baseDomain: ibmcloud.qe.devcluster.openshift.com
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 3
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
metadata:
  creationTimestamp: null
  name: pamoedo-test
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  ibmcloud:
    region: eu-de
    resourceGroupName: pamoedom-rg
publish: External
pullSecret: ***
sshKey: ***
~~~

*** PASSED ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056