-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16.z
-
None
-
False
-
Description of problem:
When creating HCP cluster (nodes from host inventory) using ACM GUI -> Infrastructure -> Clusters -> Create cluster -> Networking -> Show proxy settings, the settings are transposed to the manifest as: ``` apiVersion: hypershift.openshift.io/v1beta1 kind: HostedCluster spec: ... configuration: items: - apiVersion: config.openshift.io/v1 kind: Proxy spec: httpProxy: 'http://proxy.example.com:3128' httpsProxy: 'http://proxy.example.com:3128' noProxy: '10.0.0.0/8' ``` which is not inline with the hostedcluster CRD schema => the created cluster doesn't use specified proxy, which can be validated by checking the corresponding hostedcluster CR = proxy hostedcluster.spec.configuration.items is not present. Proxy should be transposed as hostedcluster.spec.configuration.proxy.
Version-Release number of selected component (if applicable):
4.16.z
How reproducible:
100 %
Steps to Reproduce:
1. create Host inventory 2. using ACM GUI -> Infrastructure -> Clusters -> Create cluster -> Networking -> configure proxy settings 3. check the hostedcluster CR post cluster installation starts
Actual results:
Hosted cluster misses out on proxy setting
Expected results:
Hosted cluster should be able to have proxy setting in its CR
Additional info:
As a work around proxy is being configured manually.