-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Solves #2933: Allow http_proxy, https_proxy and no_proxy environment variables in cert-manager playbook #10035
Conversation
|
Welcome @karabanov! |
Hi @karabanov. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! A couple of nits and a small typo but lgtm overall, thanks again :).
Also please rebase your PR 🙏 and also can you rename your PR like your title and perhaps link the issue in the commit description if you want keep a link to it.
@@ -7,6 +7,12 @@ cert_manager_nodeselector: {} | |||
cert_manager_dns_policy: "ClusterFirst" | |||
cert_manager_dns_config: {} | |||
|
|||
## Allow http_proxy, https_proxy and no_proxy environment variables | |||
## Issue https://github.com/kubernetes-sigs/kubespray/issues/2933 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you remove this line? IMO linking to the issue doesn't add much value here...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understood. I will remove this line
- name: HTTPS_PROXY | ||
value: "{{ cert_manager_https_proxy }}" | ||
{% endif %} | ||
{% if cert_manager_no_proxy is cert_manager_no_proxy != "" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Guessing that you missed is defined and
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My mistake. I will fix it.
## Details https://github.com/kubernetes-sigs/kubespray/blob/master/docs/proxy.md | ||
cert_manager_http_proxy: "{{ http_proxy|d('') }}" | ||
cert_manager_https_proxy: "{{ https_proxy|d('') }}" | ||
cert_manager_no_proxy: "{{ no_proxy|d('') }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a nit but style wise I think we prefer to use default
rather than just d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll change it to default
|
Looks good to me however, could you rebase to rekick the pipeline? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: karabanov The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Allow http_proxy, https_proxy and no_proxy environment variables in cert-manager playbook
What type of PR is this?
/kind feature
What this PR does / why we need it:
Allows to get TLS certificates if the cluster is located in a closed circuit with access to the Internet only through a proxy
Which issue(s) this PR fixes:
Fixes #2933
Special notes for your reviewer:
No notes
Does this PR introduce a user-facing change?:
NONE