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

A new home for 404-server (defaultbackend) #498

Closed
jonpulsifer opened this issue Sep 27, 2018 · 2 comments
Closed

A new home for 404-server (defaultbackend) #498

jonpulsifer opened this issue Sep 27, 2018 · 2 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@jonpulsifer
Copy link
Contributor

👋 we recently bumped the defaultbackend to version 1.5 in kubernetes/ingress-nginx#3125 to conceal /metrics/ behind port 10254

During that discussion a PR was merged to not require the defaultbackend service for ingress-nginx.

I originally moved the 404-server into the old kubernetes/ingress repo from contrib, but now we've gone our separate ways w/ nginx and gce so I'd like to find a new home for this image.

Should we move it here? I think so? Is there a better place? I don't think it makes sense for the ingress-nginx repo to own this image any longer.

@bowei
Copy link
Member

bowei commented Sep 27, 2018

Yes -- also, we should probably use something even simpler and smaller (thttpd?).

@rramkumar1
Copy link
Contributor

/kind cleanup

@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

No branches or pull requests

4 participants