[kubernetes-users] Getting data in and out of a job

I am setting up a go application that will create jobs. For each job execution, I need to pass a blob of parameter data into the job container, and get a blob back out. I'd like to avoid a requirement for database access in the job. Volumes seem awfully complicated, and, anyway, I don't see a

[kubernetes-users] Re: Slow response times using default Ingress on GKE

Just wanna note we're seeing this on our end too. Narrowed it down to being the GCE Ingress by testing our deployment behind the older style LoadBalancer service, where we are seeing sub-200ms responses. Also confirmed Cloudflare wasn't the issue by preventing the host from being resolved via

Re: [kubernetes-users] Ingress paths not working with dynamic endpoint

+1 to Tim. Your "rewrite-target" annotation won't work on GKE (it's only for nginx-ingress). Also note that "Services exposed through an Ingress must serve a response with HTTP 200 status to the GET requests on "/". This is used for health checking. If your application does not serve HTTP 200 on

Re: [kubernetes-users] Ingress paths not working with dynamic endpoint

Did you try /* ? https://cloud.google.com/compute/docs/load-balancing/http/url-map On Mon, May 21, 2018 at 10:44 AM Jonathan Mejias wrote: > The only way that i resolve the problem was changing to an nginx > controller, instead a gke. Installing nginx-controller with

[kubernetes-users] Re: Slow response times using default Ingress on GKE

The issue appears to be back. For the past few nights I've been seeing sporadic 4-5 second response times on calls. Again, it's calls like OPTIONS that really stand out. On Thursday, May 17, 2018 at 11:37:28 AM UTC-7, Dave Jensen wrote: > Thank you, I think this solved the issue. We set the

[kubernetes-users] Error: dial tcp getsockopt: connection timed out

Hello, I have a nine bare metal hosts setup with CentOS Atomic. I followed their guide on how to setup Kubernetes from http://www.projectatomic.io/docs/gettingstarted/ I successfully created a test service running Nginx and I was able to access it. Moving further, I got the

Re: [kubernetes-users] Kubernetes and user defined request headers (Geolocating requests)

Ok, Cool - I thought I could do it that way, just a bit worried it gets forgotten when we resize / rebuild the nodes. Thanks for the quick reply. Cheers, James On Mon, May 21, 2018 at 8:05 PM, 'Ahmet Alp Balkan' via Kubernetes user discussion and Q wrote: >

Re: [kubernetes-users] Ingress paths not working with dynamic endpoint

The only way that i resolve the problem was changing to an nginx controller, instead a gke. Installing nginx-controller with kubernetes helm and using rewrite option. Gke is limited in configuration option i do not recommend. PD: Nginx-controller uses network load balancer (TCP) not HTTP. On

[kubernetes-users] Ingress paths not working with dynamic endpoint

I have same problem. Did you mane to resolve? -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[kubernetes-users] Kubernetes and user defined request headers (Geolocating requests)

Afternoon, I saw this article the other day https://blog.doit-intl.com/farewell-maxmind-geolocating-requests-with-google-load-balancer-for-free-7938f5adbef0 describes how it is possible to configure the Googel load balancers to pass the location of the ip address to the compute instance. Does