-
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
Publish ingress-nginx service address if manual address not specified and not using host network #11879
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ThisIsQasim 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 |
Hi @ThisIsQasim. 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-sigs/prow repository. |
7f9e0fc
to
68b257e
Compare
/ok-to-test |
test failures seem related to infra provisioning and not to the PR |
Could you rebase your PR to our master branch? |
I have rebased and pushed again @tico88612 |
{% if ingress_publish_status_address != "" %} | ||
- --publish-status-address={{ ingress_publish_status_address }} | ||
{% elif ingress_nginx_host_network %} | ||
- --report-node-internal-ip-address | ||
{% else %} |
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.
The --publish-service option should be used only when publishService is enabled, as indicated in the params.tpl file.
Do the changes better:
{% elif ingress_nginx_host_network != "" %}
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.
The three options i.e. reporting a manual IP, reporting node IPs or reporting the IP of a service are mutually exclusive. So if the first two aren't configured it makes sense to default to the third. Especially since we started adding a LoadBalancer service by default so we should publish it's address by default as well.
ingress_nginx_host_network
is declared as a boolean why would I check if it is an empty string?
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.
or do you mean the following suggestion?
{% else %} | |
{% elif ingress_nginx_publish_service != "" %} |
…ed and not using host network
…ed and not using host network
What type of PR is this?
/kind feature
What this PR does / why we need it:
Advertises the correct service address if no manual address if defined and not using host networking
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: