Re: [kubernetes-users] Can't access UDP port on load balancer in kubernetes on Google kubernetes engine

2018-01-09 Thread Tameem Iftikhar
Hello, Thanks for the response. I just tried the exact same thing on google kubernetes engine. Created a two node cluster and pointed kubectl towards it: *➜ **~* kubectl get svc NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes 10.11.240.1

Re: [kubernetes-users] Can't access UDP port on load balancer in kubernetes on Google kubernetes engine

2018-01-09 Thread 'Tim Hockin' via Kubernetes user discussion and Q
Make sure all firewalls are open? I just tested it and it works: ``` $ kubectl run udp --image=ubuntu -- bash -c "while true; do sleep 10; done" deployment "udp" created $ kubectl expose deployment udp --port=12345 --protocol=UDP --type=LoadBalancer service "udp" exposed ``` Then I got the

[kubernetes-users] Can't access UDP port on load balancer in kubernetes on Google kubernetes engine

2018-01-09 Thread Tameem Iftikhar
down votefavorite I am trying to run a very simple UDP service in kubernetes on Google Cloud but am unable to access the port I am exposing to the internet. Here is the

Re: [kubernetes-users] DNS queries doesn't resolve randomly

2018-01-09 Thread John Belamaric
It is probably this: https://github.com/kubernetes/dns/issues/186 You’ll see this less with CoreDNS but it looks like we are having a similar problem but less often: https://github.com/coredns/coredns/issues/1365 John On Jan 8, 2018, at 3:57 AM,

[kubernetes-users] Re: Locust master doesn't see slaves in Kubernetes cluster

2018-01-09 Thread mderosa83
[Locust Dockerfile] FROM python:3.6.2 # Install packages COPY requirements.txt /tmp/ RUN pip install --requirement /tmp/requirements.txt # Add tasks directory COPY locust-tasks /locust-tasks # Set the entrypoint COPY docker-entrypoint.sh / RUN chmod +x /docker-entrypoint.sh ENTRYPOINT

[kubernetes-users] Locust master doesn't see slaves in Kubernetes cluster

2018-01-09 Thread mderosa83
Hi, I don't know why (I'm going crazy trying to understand the reason) but from today I have a problem with my Locust master that always returns this error: [2018-01-09 14:17:26,379] locust-master-deployment-262643481-9kfw8/INFO/locust.main: Starting web monitor at *:8089 [2018-01-09