On different cloud providers, there is probably something to do. On AWS just don't open those ports in the security group, and you are safe.
Also, you can avoid nodes having a public IP, for example. But where are you running? On Thursday, June 22, 2017, Evg <[email protected]> wrote: > Thank you for answer! > Yes indeed I use NodePorts for external load balancer, and there is need > to restrict access > to kube-proxy ports and NodePorts as well. > > What type is the service? You are probably using load balancer or >> nodeport. Right? >> >> In that case, just change them to cluster IP. >> >> Also, see here for services types: https://kubernetes.io/d >> ocs/concepts/services-networking/service/#publishing- >> services---service-types >> >> And don't hesitate to ask if it doesn't do the trick or something :) >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <javascript:_e(%7B%7D,'cvml','kubernetes-users%[email protected]');> > . > To post to this group, send email to [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
