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

Node lookup fails when --watch-namspace is present on ingress controller #342

Closed
joshrosso opened this issue Feb 24, 2017 · 0 comments · Fixed by #343
Closed

Node lookup fails when --watch-namspace is present on ingress controller #342

joshrosso opened this issue Feb 24, 2017 · 0 comments · Fixed by #343

Comments

@joshrosso
Copy link
Contributor

joshrosso commented Feb 24, 2017

When writing an ingress controller that looks up Nodes via the StoreLister the API query sent is invalid when --watch-namespace is present. Consider the following example where --watch-namespace is set to test-nm.

The ingress controller's logs will print the following:

pkg/ingress/controller/controller.go:1037: Failed to list *api.Node: the server could not find the requested resource

The API server, with --audit-log-path set, will print the following:

/api/v1/namespaces/test-nm/nodes?resourceVersion=0: (329.906µs) 404

Note the inclusion of /namespaces/test-nm resulting in a 404.

After removing --watch-namespace and redeploying, the query is valid and nodes are returned. An example query sent to the API server is now:

GET /api/v1/nodes?resourceVersion=0: (782.297µs) 200
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant