Kubernetes multi servers communication
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a question regarding Kubernetes networking.
I know that in Docker swarm if I want to run difference containers on difference servers, I need to create an overlay network, and then all the containers (from all the servers) will be attached to this network and they can communicate with each other (for example, I can ping from container A to container B).
I guess that in Kubernetes there isn't an overlay network - but another solution.
For example, I would like to create 2 linux containers on 2 servers (server 1: ubuntu, server 2: centos7), so how do the pods communicate with each other if there isn't an overlay network?
And another doubt - can I create a cluster which consists of windows and linux machines with kubernetes?I mean, a multi platform kubernetes which all the pods communicate with each other.
Thanks a lot!!
docker
asked Jan 27 at 16:53
user990631user990631
111
add a comment |
I have a question regarding Kubernetes networking.
I know that in Docker swarm if I want to run difference containers on difference servers, I need to create an overlay network, and then all the containers (from all the servers) will be attached to this network and they can communicate with each other (for example, I can ping from container A to container B).
I guess that in Kubernetes there isn't an overlay network - but another solution.
For example, I would like to create 2 linux containers on 2 servers (server 1: ubuntu, server 2: centos7), so how do the pods communicate with each other if there isn't an overlay network?
And another doubt - can I create a cluster which consists of windows and linux machines with kubernetes?I mean, a multi platform kubernetes which all the pods communicate with each other.
Thanks a lot!!
docker
asked Jan 27 at 16:53
user990631user990631
111
add a comment |
I have a question regarding Kubernetes networking.
I know that in Docker swarm if I want to run difference containers on difference servers, I need to create an overlay network, and then all the containers (from all the servers) will be attached to this network and they can communicate with each other (for example, I can ping from container A to container B).
I guess that in Kubernetes there isn't an overlay network - but another solution.
For example, I would like to create 2 linux containers on 2 servers (server 1: ubuntu, server 2: centos7), so how do the pods communicate with each other if there isn't an overlay network?
And another doubt - can I create a cluster which consists of windows and linux machines with kubernetes?I mean, a multi platform kubernetes which all the pods communicate with each other.
Thanks a lot!!
docker
asked Jan 27 at 16:53
user990631user990631
111
I have a question regarding Kubernetes networking.
I know that in Docker swarm if I want to run difference containers on difference servers, I need to create an overlay network, and then all the containers (from all the servers) will be attached to this network and they can communicate with each other (for example, I can ping from container A to container B).
I guess that in Kubernetes there isn't an overlay network - but another solution.
For example, I would like to create 2 linux containers on 2 servers (server 1: ubuntu, server 2: centos7), so how do the pods communicate with each other if there isn't an overlay network?
And another doubt - can I create a cluster which consists of windows and linux machines with kubernetes?I mean, a multi platform kubernetes which all the pods communicate with each other.
Thanks a lot!!
docker
docker
asked Jan 27 at 16:53
user990631user990631
111
asked Jan 27 at 16:53
user990631user990631
111
asked Jan 27 at 16:53
user990631user990631
111
asked Jan 27 at 16:53
user990631user990631
111
asked Jan 27 at 16:53
user990631user990631
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The topic can easy cover multiple pages, so let me try to address the basics while providing pointers for further reading.
To understand how containers/pods communicate in Kubernetes one has to understand what pod and service is.
Kubernetes pods - A Kubernetes pod is a group of containers that are deployed together on the same host.
Kubernetes service - It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
Communication between containers in the same pod.
Containers within the same pod share an IP address and port space and can find each other via localhost, thus no specific networking configuration is needed.
Note that all containers in given pod are scheduled on the same Kubernetes node.
Communication between pods.
Communication between pods is done using kubernetes service. Once you have service defined for given pod, other pods can find it using the service name.
To make analogue between Docker Swarm and Kubernates: In order to configure networking, in Docker Swarm you will define network, while in Kubernetes you will define service.
Running mixed (Windows/Linux) load on Kubernetes.
This is possible as long as you schedule your load on specific node i.e. Linux containers on Linux nodes and Windows containers on Windows nodes. Please see the answer to this question for additional details.
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398973%2fkubernetes-multi-servers-communication%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The topic can easy cover multiple pages, so let me try to address the basics while providing pointers for further reading.
To understand how containers/pods communicate in Kubernetes one has to understand what pod and service is.
Kubernetes pods - A Kubernetes pod is a group of containers that are deployed together on the same host.
Kubernetes service - It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
Communication between containers in the same pod.
Containers within the same pod share an IP address and port space and can find each other via localhost, thus no specific networking configuration is needed.
Note that all containers in given pod are scheduled on the same Kubernetes node.
Communication between pods.
Communication between pods is done using kubernetes service. Once you have service defined for given pod, other pods can find it using the service name.
To make analogue between Docker Swarm and Kubernates: In order to configure networking, in Docker Swarm you will define network, while in Kubernetes you will define service.
Running mixed (Windows/Linux) load on Kubernetes.
This is possible as long as you schedule your load on specific node i.e. Linux containers on Linux nodes and Windows containers on Windows nodes. Please see the answer to this question for additional details.
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
add a comment |
The topic can easy cover multiple pages, so let me try to address the basics while providing pointers for further reading.
To understand how containers/pods communicate in Kubernetes one has to understand what pod and service is.
Kubernetes pods - A Kubernetes pod is a group of containers that are deployed together on the same host.
Kubernetes service - It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
Communication between containers in the same pod.
Containers within the same pod share an IP address and port space and can find each other via localhost, thus no specific networking configuration is needed.
Note that all containers in given pod are scheduled on the same Kubernetes node.
Communication between pods.
Communication between pods is done using kubernetes service. Once you have service defined for given pod, other pods can find it using the service name.
To make analogue between Docker Swarm and Kubernates: In order to configure networking, in Docker Swarm you will define network, while in Kubernetes you will define service.
Running mixed (Windows/Linux) load on Kubernetes.
This is possible as long as you schedule your load on specific node i.e. Linux containers on Linux nodes and Windows containers on Windows nodes. Please see the answer to this question for additional details.
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
add a comment |
The topic can easy cover multiple pages, so let me try to address the basics while providing pointers for further reading.
To understand how containers/pods communicate in Kubernetes one has to understand what pod and service is.
Kubernetes pods - A Kubernetes pod is a group of containers that are deployed together on the same host.
Kubernetes service - It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
Communication between containers in the same pod.
Containers within the same pod share an IP address and port space and can find each other via localhost, thus no specific networking configuration is needed.
Note that all containers in given pod are scheduled on the same Kubernetes node.
Communication between pods.
Communication between pods is done using kubernetes service. Once you have service defined for given pod, other pods can find it using the service name.
To make analogue between Docker Swarm and Kubernates: In order to configure networking, in Docker Swarm you will define network, while in Kubernetes you will define service.
Running mixed (Windows/Linux) load on Kubernetes.
This is possible as long as you schedule your load on specific node i.e. Linux containers on Linux nodes and Windows containers on Windows nodes. Please see the answer to this question for additional details.
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
The topic can easy cover multiple pages, so let me try to address the basics while providing pointers for further reading.
To understand how containers/pods communicate in Kubernetes one has to understand what pod and service is.
Kubernetes pods - A Kubernetes pod is a group of containers that are deployed together on the same host.
Kubernetes service - It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
Communication between containers in the same pod.
Containers within the same pod share an IP address and port space and can find each other via localhost, thus no specific networking configuration is needed.
Note that all containers in given pod are scheduled on the same Kubernetes node.
Communication between pods.
Communication between pods is done using kubernetes service. Once you have service defined for given pod, other pods can find it using the service name.
To make analogue between Docker Swarm and Kubernates: In order to configure networking, in Docker Swarm you will define network, while in Kubernetes you will define service.
Running mixed (Windows/Linux) load on Kubernetes.
This is possible as long as you schedule your load on specific node i.e. Linux containers on Linux nodes and Windows containers on Windows nodes. Please see the answer to this question for additional details.
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
answered Mar 12 at 12:19
Filip NikolovFilip Nikolov
5113
5113
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398973%2fkubernetes-multi-servers-communication%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
