RHOCP 4 should be able to utilize a proxy with complex password security
Issue
-
OCP should be able to utilize a proxy with complex password security requirements
and HTTP_PROXY / HTTPS_PROXY variable should be correctly encoded to match
systemd requirements -
System wide proxy is not being used
-
A URL encoded password will yield an unknown specifier (from systemd's perspective, and therefore needs to be double escaped). However systemd will reject any unknown '%' specifiers. See https://github.com/systemd/systemd/blob/a1b2c92d8290c76a29ccd0887a92ac064e1bb5a1/NEWS#L10
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.