-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Unable to disable HTTP access on ingress #6590
Comments
Closing. This annotation is supported only by ingress-gce Edit: there is no way to disable HTTP for a particular ingress. If you want to block all access to port 80, then do not expose the port in the ingress-nginx service. |
I changed all port
I am not sure if this is a feasible reason to close the ticket. I wouldn't close the ticket just because there is an unused piece of code/line I have seen. It is there as an information purposes. I was trying to be as descriptive as possible by providing info on, for example, what else I have tried. Feels more like shrug off. |
I am quite new to Kubernetes and could not find this easily. Can you please give any suggestion how to not expose the port 80 in the ingress-nginx service? Because I do not create any Kubernetes Service for Ingress to work, I only have a yaml for creating the Ingress object and it works. But I really need to stop serving on port 80 completely and keep only port 443 that accepts connections only with the authorized client certificate. |
If any one still looking for a solution adding the tls attribute will only expose the https port. Here is an example :
|
Hi,
Not sure if this is a bug or not so asking here. I followed the doc but nothing seems specific. Tried
annotations
as listed below but no luck. Coming from kubernetes repo.Thanks
What happened:
Unable to disable HTTP requests.
This works
curl --request GET http://my-address-finder.com
but it shouldn't.What you expected to happen:
Allow only HTTPS access.
Only this should work
curl --insecure --request GET https://my-address-finder.com
which already works so no problem.How to reproduce it (as minimally and precisely as possible):
ingress.yaml
service.yaml
deployment.yaml
ingress
service
secret
Environment:
kubectl version
):Using minikube.
cat /etc/os-release
):uname -a
):Ingress Controller details.
$ kubectl get pods --all-namespaces | grep ingress kube-system ingress-nginx-admission-create-tpbrr 0/1 Completed 0 3d kube-system ingress-nginx-admission-patch-vbwvm 0/1 Completed 2 3d kube-system ingress-nginx-controller-799c9469f7-tkz48 1/1 Running 2 3d
Looks like my version is converted to
extensions/v1beta1
!!!If I use the
networking.k8s.io/v1beta1
version, HTTP is disabled however why suggested versionnetworking.k8s.io/v1
won't work?My HTTP requests are successfully redirected to HTTPS here.
/kind bug
The text was updated successfully, but these errors were encountered: