Re: [kubernetes-users] Kubernetes Ingress HTTP Load Balancer with port range

2018-05-17 Thread Jonathan Mejias
Yeah, i know that does so many things but How can i create virtual host using kubernetes and using HTTP Load Balancer types? I just need to use PATHS for my dynamic endpoints applications. And i need to use the better practices in that. regards 2018-05-17 11:00 GMT-04:00 'Tim Hockin' via

Re: [kubernetes-users] Kubernetes Ingress HTTP Load Balancer with port range

2018-05-17 Thread 'Tim Hockin' via Kubernetes user discussion and Q
Kubernetes' Ingress abstraction does what you want. On Wed, May 16, 2018 at 6:38 PM Jonathan Mejias wrote: > Im using kubernetes to deploy apps, how can i create that virtual host > into a container cluster? > > On Wed, May 16, 2018, 19:36 'Tim Hockin' via Kubernetes user

Re: [kubernetes-users] Kubernetes Ingress HTTP Load Balancer with port range

2018-05-16 Thread 'Tim Hockin' via Kubernetes user discussion and Q
HTTP gives you a much better solution - virtual hosts. The 'host' header tells your HTTP ingress which logical service to access. e.g. `curl -h 'host: foo.com' http://210.210.210.22:80/` is different than `curl -h 'host: bar.com' http://210.210.210.22:80/` On Wed, May 16, 2018 at 1:19 PM

[kubernetes-users] Kubernetes Ingress HTTP Load Balancer with port range

2018-05-16 Thread Jonathan Mejías
Hi How do i to create a HTTP load balancer with kubernetes ingress? Example: SVC-1 . -- 210.210.210.22:*80 (internet)* SVC-2 . -- 210.210.210.22:*81 (internet)* SVC-3 . -- 210.210.210.22:*82 (internet)* services created in type NodePort, but what are the definitios for

Re: [kubernetes-users] Kubernetes ingress

2018-04-29 Thread Kanthi P
ok, thanks for the info On Sat, Apr 28, 2018 at 2:31 PM, 'Tim Hockin' via Kubernetes user discussion and Q wrote: > Ingress is sort of the lowest-common-API across many platforms. I am not > sure that the majority of them can support it natively. I think

Re: [kubernetes-users] Kubernetes ingress

2018-04-28 Thread 'Tim Hockin' via Kubernetes user discussion and Q
Ingress is sort of the lowest-common-API across many platforms. I am not sure that the majority of them can support it natively. I think it's logical, but may not be practical yet. On Sat, Apr 28, 2018, 7:41 AM Kanthi P wrote: > ohk Tim. Does it sound like a good

Re: [kubernetes-users] Kubernetes ingress

2018-04-28 Thread Kanthi P
ohk Tim. Does it sound like a good thing to add? Let me share our usecase. We are building a datascience platform using kubernetes. We have datascience app which uses tensorflow internally, this runs as a service in kubernetes cluster. And we configured ingress controller for this service.

Re: [kubernetes-users] Kubernetes ingress

2018-04-28 Thread 'Tim Hockin' via Kubernetes user discussion and Q
Ingress does not do prefix stripping or URL munging by default, as not all platforms support it. I verified against the Google implementation, it passes the URL path through directly. On Sat, Apr 28, 2018, 6:09 AM Kanthi P wrote: > Thanks David for the example. I

Re: [kubernetes-users] Kubernetes ingress

2018-04-27 Thread Kanthi P
Thanks David for the example. I tried it, with this we can only redirect /test/data to /data, but we won't be able to redirect /test to /. We actually want /test to remain redirected to / itself and /test/data to redirect to /data and /test/data/runs to /data/runs and so on. So in short, we

Re: [kubernetes-users] Kubernetes ingress

2018-04-27 Thread David Rosenstrauch
If you were using the nginx ingress, you would do it like this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: test-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /data nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - http:

[kubernetes-users] Kubernetes ingress

2018-04-27 Thread Kanthi P
Hi, Need some help with ingress controller we want to redirect a http request say //xyz to be mapped to a service in the backend. And the service should receive the request as /xyz How do we annotate this in the ingress resource? Have configured the ingress resource as shown: apiVersion:

Re: [kubernetes-users] kubernetes ingress annotation syntax

2017-06-12 Thread 'Timo Reimann' via Kubernetes user discussion and Q
Some annotations are already shared by multiple Ingress controller implementations. It'd be nice to come up with an effort and associated prefix that allows for some level of standardization. -- You received this message because you are subscribed to the Google Groups "Kubernetes user

Re: [kubernetes-users] kubernetes ingress annotation syntax

2017-06-11 Thread aledbf
> Yeah, the naming on those is not very well defined :) Can you mention which ones? On Thursday, June 8, 2017 at 11:42:49 PM UTC-4, Tim Hockin wrote: > Yeah, the naming on those is not very well defined :) > > On Wed, Jun 7, 2017 at 9:54 PM, wrote: > > There is already a

Re: [kubernetes-users] kubernetes ingress annotation syntax

2017-06-08 Thread 'Tim Hockin' via Kubernetes user discussion and Q
Yeah, the naming on those is not very well defined :) On Wed, Jun 7, 2017 at 9:54 PM, wrote: > There is already a catalog in the ingress repository. This is the link > https://github.com/kubernetes/ingress/blob/master/docs/annotations.md > > > On Thursday, June 8, 2017 at

Re: [kubernetes-users] kubernetes ingress annotation syntax

2017-06-07 Thread aledbf
There is already a catalog in the ingress repository. This is the link https://github.com/kubernetes/ingress/blob/master/docs/annotations.md On Thursday, June 8, 2017 at 12:41:16 AM UTC-4, Tim Hockin wrote: > We have done a poor job in th epast of being clear when an annotation > was particular

[kubernetes-users] kubernetes ingress annotation syntax

2017-06-07 Thread Paul Mazzuca
Hey everyone, I have noticed that the docs for K8s have used different syntax for annotations in yaml files. For example, on this page https://cloud.google.com/container-engine/docs/tutorials/http-balancer, kubernetes.io/ingress.global-static-ip-name While on this page (the main