Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand documentation on HTTP_PROXY, HTTPS_PROXY, NO_PROXY #17398

Open
juanvallejo opened this issue Nov 20, 2017 · 4 comments
Open

Expand documentation on HTTP_PROXY, HTTPS_PROXY, NO_PROXY #17398

juanvallejo opened this issue Nov 20, 2017 · 4 comments
Assignees
Labels
area/documentation component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2

Comments

@juanvallejo
Copy link
Contributor

Right now, current documentation covers proxy enrivonment variables
by mentioning that they can be set in podSpec templates, and as part of a
node's configuration. Documentation does not mention, however, that these
environment variables can also be set on the environment from which an
oc binary is being executed.

It would be good to expand docs (and even cli help output) to mention that
these environment variables are taken into account by an oc binary, and give
some use-cases on when they might be used by oc to talk to a master.

cc @gabemontero @openshift/cli-review @bparees

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 25, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 28, 2018
@bparees
Copy link
Contributor

bparees commented Mar 28, 2018

/remove-lifecycle rotten
/lifecycle frozen

@openshift-ci-robot openshift-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 28, 2018
@bparees
Copy link
Contributor

bparees commented Mar 28, 2018

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2
Projects
None yet
Development

No branches or pull requests

5 participants