You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it seems that all companies, apart from Intel, have been missing out on how fun and productive it is to use proxies, our machine has to have a special configuration and / or adapt the ansible scripts to use proxies whenever those are set up in the environment.
As I'm really trying to not be selfish, I'll let others have this kind of fun this week, and I'll summon @GabyCT here.
One easy way to reproduce this is just by cloning the operator repo in the machine, and trying to run the run-local.sh script. which will fail straight away trying to download the go package.
The text was updated successfully, but these errors were encountered:
As it seems that all companies, apart from Intel, have been missing out on how fun and productive it is to use proxies, our machine has to have a special configuration and / or adapt the ansible scripts to use proxies whenever those are set up in the environment.
As I'm really trying to not be selfish, I'll let others have this kind of fun this week, and I'll summon @GabyCT here.
@GabyCT, enjoy. :-)
One easy way to reproduce this is just by cloning the operator repo in the machine, and trying to run the
run-local.sh
script. which will fail straight away trying to download the go package.The text was updated successfully, but these errors were encountered: