Minor Proposed title of this feature request
Add proxy settings to coreos toolbox
What is the nature and description of the request?
Currently we set the httpProxy in the install-config.yaml when installing a Openshift cluster. It would be nice if the toolbox uses this proxy by default:
When starting toolbox it cannot reach registry.redhat.io:
[root@worker-0 ~]# toolbox Trying to pull registry.redhat.io/rhel9/support-tools:latest... WARN[0020] Failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/rhel9/support-tools:latest: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp: lookup registry.redhat.io on 10.123.127.249:53: read udp 10.124.8.149:60265->10.123.127.249:53: i/o timeout
When defining the HTTPS_PROXY that is set in install-config.yaml:
[root@worker-0 ~]# export HTTPS_PROXY=http://10.x.x.x:3128 [root@worker-0 ~]# export HTTP_PROXY=http://10.x.x.x:3128 [root@worker-0 ~]# toolbox Trying to pull registry.redhat.io/rhel9/support-tools:latest... Getting image source signatures Checking if image destination supports signatures Copying blob 7b3dd25bf011 done Copying blob a169572c7b0e done Copying config 42f4a0cc4e done Writing manifest to image destination Storing signatures 42f4a0cc4e00678bc181a85dac8113660aab7e10af0e29af61c0b1645e7861b4 Spawning a container 'toolbox-root' with image 'registry.redhat.io/rhel9/support-tools' Detected RUN label in the container image. Using that as the default... 627423d730100bb8d4d1dcecf170de94f1a1410cb398c52f80387d01faddee91 toolbox-root Container started successfully. To exit, type 'exit'.
Why does the customer need this? (List the business requirements here)
It would be a great advantage if we could assist the customer with this.
List any affected packages or components.
- Toolbox