Kubernetes IP service IP and ports












0















I've deployed a hello-world application on my Kubernetes cluster. When I access the app via <cluster ip>:<port> in my browser I get the following webpage: hello-kuleuven app webpage.



I understand that from outside the cluster you have to access the app via the cluster IP and the port specified in the deployment file (which in my case is 30001). From inside the cluster you have to contact the master node with its local IP and another port number, in my case 10.111.152.164:8080.



My question is about the last line of the webpage:



Kubernetes listening in 443 available at tcp://10.96.0.1:443


Since, the service is already accessible from inside and outside the cluster by other ports and IP's, I'm not sure what this does.






kubernetes







share|improve this question

























  • Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

    – Emruz Hossain
    Nov 28 '18 at 13:41











  • I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

    – Charles Van Damme
    Nov 28 '18 at 13:48
















0















I've deployed a hello-world application on my Kubernetes cluster. When I access the app via <cluster ip>:<port> in my browser I get the following webpage: hello-kuleuven app webpage.



I understand that from outside the cluster you have to access the app via the cluster IP and the port specified in the deployment file (which in my case is 30001). From inside the cluster you have to contact the master node with its local IP and another port number, in my case 10.111.152.164:8080.



My question is about the last line of the webpage:



Kubernetes listening in 443 available at tcp://10.96.0.1:443


Since, the service is already accessible from inside and outside the cluster by other ports and IP's, I'm not sure what this does.






kubernetes







share|improve this question

























  • Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

    – Emruz Hossain
    Nov 28 '18 at 13:41











  • I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

    – Charles Van Damme
    Nov 28 '18 at 13:48














0












0








0








I've deployed a hello-world application on my Kubernetes cluster. When I access the app via <cluster ip>:<port> in my browser I get the following webpage: hello-kuleuven app webpage.



I understand that from outside the cluster you have to access the app via the cluster IP and the port specified in the deployment file (which in my case is 30001). From inside the cluster you have to contact the master node with its local IP and another port number, in my case 10.111.152.164:8080.



My question is about the last line of the webpage:



Kubernetes listening in 443 available at tcp://10.96.0.1:443


Since, the service is already accessible from inside and outside the cluster by other ports and IP's, I'm not sure what this does.






kubernetes







share|improve this question
















I've deployed a hello-world application on my Kubernetes cluster. When I access the app via <cluster ip>:<port> in my browser I get the following webpage: hello-kuleuven app webpage.



I understand that from outside the cluster you have to access the app via the cluster IP and the port specified in the deployment file (which in my case is 30001). From inside the cluster you have to contact the master node with its local IP and another port number, in my case 10.111.152.164:8080.



My question is about the last line of the webpage:



Kubernetes listening in 443 available at tcp://10.96.0.1:443


Since, the service is already accessible from inside and outside the cluster by other ports and IP's, I'm not sure what this does.






kubernetes




kubernetes






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 '18 at 15:11









Emruz Hossain

1,146511




1,146511










asked Nov 28 '18 at 13:24









Charles Van DammeCharles Van Damme

83




83













  • Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

    – Emruz Hossain
    Nov 28 '18 at 13:41











  • I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

    – Charles Van Damme
    Nov 28 '18 at 13:48



















  • Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

    – Emruz Hossain
    Nov 28 '18 at 13:41











  • I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

    – Charles Van Damme
    Nov 28 '18 at 13:48

















Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

– Emruz Hossain
Nov 28 '18 at 13:41





Can you please point us to the app you are trying to deploy? It seem's it is the address of Kubernetes API Server.

– Emruz Hossain
Nov 28 '18 at 13:41













I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

– Charles Van Damme
Nov 28 '18 at 13:48





I'm deploying tutum/hello-world from Docker Hub. OK, but if that's the IP of the API Server, than the 10.111.152.164 (see webpage picture) is the IP of the service itself, right? Why do we need both?

– Charles Van Damme
Nov 28 '18 at 13:48












1 Answer
1






active

oldest

votes


















1














The IP 10.96.0.1 is a cluster IP of kube-dns service. You can see it using



kubectl get svc -n kube-apiserver


Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service’s IP to resolve DNS names.



So every pod you deploy uses kube-dns service (ClusterIP 10.96.0.1) to resolve the dns names.



Read more about kube dns at kubernetes official document here






share|improve this answer
























  • Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

    – Charles Van Damme
    Nov 28 '18 at 14:39











  • DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

    – Prafull Ladha
    Nov 28 '18 at 14:51











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53520497%2fkubernetes-ip-service-ip-and-ports%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









1














The IP 10.96.0.1 is a cluster IP of kube-dns service. You can see it using



kubectl get svc -n kube-apiserver


Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service’s IP to resolve DNS names.



So every pod you deploy uses kube-dns service (ClusterIP 10.96.0.1) to resolve the dns names.



Read more about kube dns at kubernetes official document here






share|improve this answer
























  • Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

    – Charles Van Damme
    Nov 28 '18 at 14:39











  • DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

    – Prafull Ladha
    Nov 28 '18 at 14:51
















1














The IP 10.96.0.1 is a cluster IP of kube-dns service. You can see it using



kubectl get svc -n kube-apiserver


Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service’s IP to resolve DNS names.



So every pod you deploy uses kube-dns service (ClusterIP 10.96.0.1) to resolve the dns names.



Read more about kube dns at kubernetes official document here






share|improve this answer
























  • Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

    – Charles Van Damme
    Nov 28 '18 at 14:39











  • DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

    – Prafull Ladha
    Nov 28 '18 at 14:51














1












1








1







The IP 10.96.0.1 is a cluster IP of kube-dns service. You can see it using



kubectl get svc -n kube-apiserver


Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service’s IP to resolve DNS names.



So every pod you deploy uses kube-dns service (ClusterIP 10.96.0.1) to resolve the dns names.



Read more about kube dns at kubernetes official document here






share|improve this answer













The IP 10.96.0.1 is a cluster IP of kube-dns service. You can see it using



kubectl get svc -n kube-apiserver


Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service’s IP to resolve DNS names.



So every pod you deploy uses kube-dns service (ClusterIP 10.96.0.1) to resolve the dns names.



Read more about kube dns at kubernetes official document here







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 28 '18 at 14:06









Prafull LadhaPrafull Ladha

3,7231623




3,7231623













  • Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

    – Charles Van Damme
    Nov 28 '18 at 14:39











  • DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

    – Prafull Ladha
    Nov 28 '18 at 14:51



















  • Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

    – Charles Van Damme
    Nov 28 '18 at 14:39











  • DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

    – Prafull Ladha
    Nov 28 '18 at 14:51

















Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

– Charles Van Damme
Nov 28 '18 at 14:39





Thanks, but I thought DNS was an optional feature? if that's the IP of the DNS service, what's the other internal IP than (10.111.152.164)?

– Charles Van Damme
Nov 28 '18 at 14:39













DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

– Prafull Ladha
Nov 28 '18 at 14:51





DNS is an optional feature but when you deploy cluster using kubernetes the hard way, setting up everything manually. If you use any tool like kubeadm to deploy it comes for service discovery. It is an optional feature but also at the same time recommend way to do service discovery. The IP 10.111.152.164 is the clusterIP to your service it means that the xyz service will have same internal IP and all pods connected through that service can be accessed through that IP

– Prafull Ladha
Nov 28 '18 at 14:51




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53520497%2fkubernetes-ip-service-ip-and-ports%23new-answer', 'question_page');
}
);

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







-

Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more