[kubernetes-users] Comparison / Suggestions on kubeadm alternatives for HA implementations for CentOS/RHEL on bare metal / VSphere + Cloud

Hello all! I have started with kubeadm on single host and made it work on AWS / Centos, but not on CentOS vagrant boxes for some reason (https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/). Then I tested kubeadm HA guide and could not make it work at all

Re: [kubernetes-users] Change the default name of Load Balancer

I dont know if i explain myself well.. I want to use "apliccation-loadbalancer" name, instead "jsvaq1568njsuwha38." when expose a deployment.yaml like loadBalancer type. I miss something? Regards! On Wed, May 23, 2018, 20:33 'Tim Hockin' via Kubernetes user discussion and Q

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

can you try to repro with a manual LB and /* - that should match all sub-paths. On Wed, May 23, 2018 at 1:11 PM Jonathan Mejias wrote: > Ahmet i did all that you mention it. > > /angular, /angular/, /angular/* and if a get the healtcheck to " / " i > will get the response

Re: [kubernetes-users] Change the default name of Load Balancer

The problem is that we only get 63 characters to make a unique name, and both kubernetes namespace and service names can be that long themselves, and even then they are not unique across clusters. We could use the UUID and up to 27 characters of the combination of those names, but then we have a

[kubernetes-users] Change the default name of Load Balancer

Hi. By default kubernetes when expose the Google Load Balancer gives a name like "3efre2udfi9w2du9qwefds200992di" there is a way to change that name to one more human readble? Regards -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion

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

Ahmet i did all that you mention it. /angular, /angular/, /angular/* and if a get the healtcheck to " / " i will get the response of a default backend (404). Insted my app have an "healthCheck" path response (resolve an HTTP 200). My path didn`t work. All the problems get solution when you

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

This looks something to do with google load balancer or the kube-proxy. I setup a google Http load balancer pointing to the NodePort and see the same issue. If I open up the service as LoadBalancer and access it directly I don’t see any issues. On 5/21/18, 10:07 PM,