This is not well supported via the ingress mechanism and is an open issue. There is a work around for tcp or udp traffic using nginx-ingress which will map an exposed port to a kubernetes service using a configmap. See this doc. Start the ingress controller with the tcp-services-configmap (and/or udp-services-configmap) argument. args: – “/nginx-ingress-controller” … Read more
You can use the annotation nginx.ingress.kubernetes.io/proxy-body-size to set the max-body-size option right in your Ingress object instead of changing a base ConfigMap. Here is the example of usage: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: my-app annotations: nginx.ingress.kubernetes.io/proxy-body-size: “50m” …
No. From the kubernetes documentation: An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically uses a service of type Service.Type=NodePort or Service.Type=LoadBalancer. It may be possible to customize a LoadBalancer on a cloud provider like AWS to listen on other ports.
I would like to simplify the answer a bit for those who are relatively new to Kubernetes and its ingress options. There are 2 separate things that need to be present for ingress(es) to work: Ingress Controller: a separate DaemonSet (a controller which runs on all nodes, including any future ones) along with a Service … Read more
You can use server-snippet annotation. This seems like exactly what you want to achieve.
Another option you have is to remove the Validating Webhook entirely: kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission I found I had to do that on another issue, but the workaround/solution works here as well. This isn’t the best answer; the best answer is to figure out why this doesn’t work. But at some point, you live … Read more
An ExternalName service is a special case of service that does not have selectors and uses DNS names instead. You can find out more about ExternalName service from the official Kubernetes documentation: When you want to access a service from a different namespace, your yaml could, for example, look like this: kind: Service apiVersion: v1 … Read more
[*] Provided you got kubectl in your pod and have access to the api-server, you can get all endpoint adressess and pass them to curl: kubectl get endpoints <servicename> \ -o jsonpath=”{.subsets[*].addresses[*].ip}” | xargs curl Alternative without kubectl in pod: the recommended way to access the api server from a pod is by using kubectl … Read more
Load Balancer: A kubernetes LoadBalancer service is a service that points to external load balancers that are NOT in your kubernetes cluster, but exist elsewhere. They can work with your pods, assuming that your pods are externally routable. Google and AWS provide this capability natively. In terms of Amazon, this maps directly with ELB and … Read more