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

Remove useless nodeip calls and deprecate --force-namespace-isolation #3887

Merged
merged 1 commit into from
Mar 11, 2019

Conversation

alexkursell
Copy link
Contributor

@alexkursell alexkursell commented Mar 11, 2019

What this PR does / why we need it: We were making a useless call to get the node information for our pod, information which was then never used. This is normally fine, but when the permissions do not exist to access node info, this caused an error. (see #3817)

Which issue this PR fixes: fixes #3817

Special notes for your reviewer:

There is still one condition where ingress-nginx needs to get the node info (to get the external IP address): when neither --publish-service nor --publish-status-address are set. It doesn't look like the same information can't be retrieved from the pod object, so it looks like this use needs to be kept around. Would it be better to just document the fact that without either of these two flags, we must make cluster level API calls, or would it be better to keep the --force-namespace-isolation flag and make creating an ingress-nginx instance with --force-namespace-isolation but neither --publish-service nor --publish-status-address an error?

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 11, 2019
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 11, 2019
@aledbf
Copy link
Member

aledbf commented Mar 11, 2019

@alexkursell please don't remove the GetNodeIPOrName method. This is used in beremetal and scenarios like minikube. Maybe the call to that function could be ommited if the flags --publish-service or --publish-status-address are used.

@aledbf
Copy link
Member

aledbf commented Mar 11, 2019

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 11, 2019
@alexkursell
Copy link
Contributor Author

@alexkursell please don't remove the GetNodeIPOrName method. This is used in beremetal and scenarios like minikube. Maybe the call to that function could be ommited if the flags --publish-service or --publish-status-address are used.

I didn't remove the method, but calling it and storing the result in PodInfo doesn't seem to do anything. I can't find anywhere where that field is accessed.

@aledbf
Copy link
Member

aledbf commented Mar 11, 2019

I didn't remove the method, but calling it and storing the result in PodInfo doesn't seem to do anything.

Sorry, you are right. The method is called and used only as the last resource in the status update.

@aledbf aledbf removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 11, 2019
@aledbf
Copy link
Member

aledbf commented Mar 11, 2019

@alexkursell please squash the commits and this lgtm

@aledbf
Copy link
Member

aledbf commented Mar 11, 2019

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 11, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, alexkursell

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2019
@k8s-ci-robot k8s-ci-robot merged commit 55bda6e into kubernetes:master Mar 11, 2019
@alexkursell alexkursell deleted the remove-nodeip branch March 12, 2019 14:11
hypnoce added a commit to hypnoce/charts that referenced this pull request May 2, 2019
hypnoce added a commit to hypnoce/charts that referenced this pull request May 2, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887.

Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce added a commit to hypnoce/charts that referenced this pull request May 8, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887.

Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce added a commit to hypnoce/charts that referenced this pull request May 20, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887.

Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce added a commit to hypnoce/charts that referenced this pull request May 20, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887.

Signed-off-by: Francois JACQUES <fjacques@murex.com>
k8s-ci-robot pushed a commit to helm/charts that referenced this pull request May 20, 2019
…12510) as it is not needed per kubernetes/ingress-nginx#3887. (#13460)

Signed-off-by: Francois JACQUES <fjacques@murex.com>
amine7536 pushed a commit to amine7536/charts that referenced this pull request May 21, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887. (helm#13460)

Signed-off-by: Francois JACQUES <fjacques@murex.com>
eyenx pushed a commit to eyenx/charts that referenced this pull request May 28, 2019
…elm#12510) as it is not needed per kubernetes/ingress-nginx#3887. (helm#13460)

Signed-off-by: Francois JACQUES <fjacques@murex.com>
dmitry-j-mikhin pushed a commit to dmitry-j-mikhin/ingress-chart that referenced this pull request Feb 27, 2020
…12510) as it is not needed per kubernetes/ingress-nginx#3887. (#13460)

Signed-off-by: Francois JACQUES <fjacques@murex.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Controller makes cluster level API calls with namespace isolation enabled
3 participants