nginx-ingress

TCP ingress support in Kubernetes

时间秒杀一切 提交于 2019-12-01 12:30:19
It seems to be TCP and UDP support is going to be deprecated in next version of ingress-nginx controller . Any other ingress controllers supports TCP and UDP ? or any other solutions for exposing non-http ports outside kubernetes ? kubernetes beginner here * The nginx-ingress (and the Ingress resource in K8s for that matter) is a layer 7 facility and doesn't support layer 4, in any case, layer 4 might be supported at some point in the future. Note that nginx itself supports layer 4 traffic but not the K8s Ingress. If you like to directly terminate TCP or UDP you can use standard Kubernetes

TCP ingress support in Kubernetes

点点圈 提交于 2019-12-01 10:57:04
问题 It seems to be TCP and UDP support is going to be deprecated in next version of ingress-nginx controller . Any other ingress controllers supports TCP and UDP ? or any other solutions for exposing non-http ports outside kubernetes ? kubernetes beginner here * 回答1: The nginx-ingress (and the Ingress resource in K8s for that matter) is a layer 7 facility and doesn't support layer 4, in any case, layer 4 might be supported at some point in the future. Note that nginx itself supports layer 4

ingress-nginx - create one ingress per host? Or combine many hosts into one ingress and reload?

独自空忆成欢 提交于 2019-11-29 07:55:39
I'm building a service where users can build web apps - these apps will be hosted under a virtual DNS name *.laska.io For example, if Tom and Jerry both built an app, they'd have it hosted under: tom.laska.io jerry.laska.io Now, suppose I have 1000 users. Should I create one big ingress that looks like this? apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx-ingress annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - host: tom.laska.io http: paths: - backend: serviceName: nginx-service servicePort: 80 - host: jerry

ingress-nginx - create one ingress per host? Or combine many hosts into one ingress and reload?

房东的猫 提交于 2019-11-28 01:36:51
问题 I'm building a service where users can build web apps - these apps will be hosted under a virtual DNS name *.laska.io For example, if Tom and Jerry both built an app, they'd have it hosted under: tom.laska.io jerry.laska.io Now, suppose I have 1000 users. Should I create one big ingress that looks like this? apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx-ingress annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: -