Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-8951

No way to set PROXY vars on Submariner Gateway Pod

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • None
    • False
    • Submariner Sprint 2023-15, Submariner Sprint 2024-16, Submariner Sprint 2024-17, Submariner Sprint 2024-18, Submariner Sprint 2024-19, Submariner Sprint 2024-20, Submariner Sprint 2024-21, Submariner Sprint 2024-22, Submariner Sprint 2024-23
    • Important
    • No

      Description of problem:

      There doesn't seem to be a way to set PROXY environment variables in the submariner gateway pod.

      In a OCP4 cluster behind a proxy with a global proxy configured the submariner operator pod gets NO_PROXY, HTTP_PROXY, and HTTPS_PROXY env vars set. The gateway pod does not. There doesn't seem to be a set environment vars in the operator`kind: Submariner` yaml either.

      As the gateway pod isn't configured for proxy access or you can't configure it we get a bunch of time out errors.

      ain Error creating local endpoint object error="could not determine public IP: Unable to resolve public IP by any of the resolver methods: [\nResolver[\"api:ifconfig.me\"]: retrieving public IP from https://ifconfig.me: Get \"https://ifconfig.me\": context deadline exceeded (Client.Timeout exceeded while awaiting headers), \nResolver[\"api:ipecho.net/plain\"]: retrieving public IP from https://ipecho.net/plain: Get \"https://ipecho.net/plain\": context deadline exceeded (Client.Timeout exceeded while awaiting headers), \nResolver[\"api:4.icanhazip.com\"]: retrieving public IP from https://4.icanhazip.com: Get \"https://4.icanhazip.com\": context deadline exceeded (Client.Timeout exceeded while awaiting headers), \nResolver[\"api:4.tnedi.me\"]: retrieving public IP from https://4.tnedi.me: Get \"https://4.tnedi.me\": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 

      If we could have a way to set proxy env vars we wouldn't get these errors.

       

      Thanks!

            rh-ee-vthapar Vishal Thapar
            pthomson1@redhat.com Philip Thomson (Inactive)
            Maxim Babushkin Maxim Babushkin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: