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

Allow http_proxy environment variables for cert-manager #2933

Closed
fllaca opened this issue Jun 25, 2018 · 4 comments · Fixed by #10162
Closed

Allow http_proxy environment variables for cert-manager #2933

fllaca opened this issue Jun 25, 2018 · 4 comments · Fixed by #10162
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@fllaca
Copy link

fllaca commented Jun 25, 2018

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Environment:

  • Cloud provider or hardware configuration: any

  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"): any

  • Version of Ansible (ansible --version): any

Kubespray version (commit) (git rev-parse --short HEAD):

Network plugin used: any

Copy of your inventory file: -

Command used to invoke ansible: -

Output of ansible run:

Anything else do we need to know:

When running a cluster behind a proxy, Cert Manager may need the http_proxy environment variables to reach ACME, Route53 or whatever to perform certificates renewals. I've submitted a PR with a solution proposal for this: #2934

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 11, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-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 May 11, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

karabanov added a commit to karabanov/kubespray that referenced this issue May 30, 2023
…xy environment variables in cert-manager playbook
k8s-ci-robot pushed a commit that referenced this issue Jun 1, 2023
alekseyolg pushed a commit to alekseyolg/kubespray that referenced this issue Jun 21, 2023
pedro-peter pushed a commit to pedro-peter/kubespray that referenced this issue May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
3 participants