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

Instructions for setting up with AWS refer to a nonexistent resource #2278

Closed
bartelsb opened this issue Mar 30, 2018 · 0 comments · Fixed by #2282
Closed

Instructions for setting up with AWS refer to a nonexistent resource #2278

bartelsb opened this issue Mar 30, 2018 · 0 comments · Fixed by #2282

Comments

@bartelsb
Copy link

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
Yes

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
AWS

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

NGINX Ingress controller version:
Current

Kubernetes version (use kubectl version):
1.9.3

Environment:

  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A

What happened:
When I attempt to retrieve https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/patch-deployment.yaml, as instructed by the docs for using the network load balancer on AWS, I get a 404. I have verified that the file doesn't exist in the project.

What you expected to happen:
I expected to download a yaml file.

How to reproduce it (as minimally and precisely as possible):
Curl the URL specified above.

Anything else we need to know:
I'm just looking for what file I should be using instead.

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