Kubernetes requires all nodes that run pods to have the kubelet running to manage the containers. This also means that everything in the cluster needs to be part of the same overlay network.
This can be done "remotely" with overlay software like weaveworks system. But for most practical deployments, this is not what Kubernetes is going to do well. On Dec 2, 2016 20:55, <[email protected]> wrote: > > What do you mean with "remote deploying"? Is there any way to deploy > that is not > > remote and used today? Sorry, I really don't follow. Can you please > elaborate? :) > > Sure! I mean that I don't want to use Kubernetes to deploy and monitor > micro services on a cluster composed by machines within the same network. I > want to find a tool to deliver micro services to machines outside my > network. The job that I have to take care of, is moving a micro service > from point A to point b over the internet. > I hope this is more clear. > > -- > 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. > -- 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.
