Please Example Kubernetes External Address vs Internal Addresses












1















In a vmware environment, should the external address become populated with the VM's (or hosts) ip address?



I have three clusters, and have found that only those using a "cloud provider" have external addresses when I run kubectl get nodes -o wide. It is my understanding that the "cloud provider" plugin (GCP, AWS, Vmware, etc) is what assigns the public ip address to the node.



KOPS deployed to GCP = external address is the real public IP addresses of the nodes.



Kubeadm deployed to vwmare, using vmware cloud provider = external address is the same as the internal address (a private range).



Kubeadm deployed, NO cloud provider = no external ip.



I ask because I have a tool that scrapes /api/v1/nodes and then interacts with each host that is finds, using the "external ip". This only works with my first two clusters.



My tool runs on the local network of the clusters, should it be targeting the "internal ip" instead? In other words, is the internal ip ALWAYS the IP address of the VM or physical host (when installed on bare metal).



Thank you










share|improve this question























  • It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

    – jsirianni
    Nov 15 '18 at 18:44
















1















In a vmware environment, should the external address become populated with the VM's (or hosts) ip address?



I have three clusters, and have found that only those using a "cloud provider" have external addresses when I run kubectl get nodes -o wide. It is my understanding that the "cloud provider" plugin (GCP, AWS, Vmware, etc) is what assigns the public ip address to the node.



KOPS deployed to GCP = external address is the real public IP addresses of the nodes.



Kubeadm deployed to vwmare, using vmware cloud provider = external address is the same as the internal address (a private range).



Kubeadm deployed, NO cloud provider = no external ip.



I ask because I have a tool that scrapes /api/v1/nodes and then interacts with each host that is finds, using the "external ip". This only works with my first two clusters.



My tool runs on the local network of the clusters, should it be targeting the "internal ip" instead? In other words, is the internal ip ALWAYS the IP address of the VM or physical host (when installed on bare metal).



Thank you










share|improve this question























  • It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

    – jsirianni
    Nov 15 '18 at 18:44














1












1








1


1






In a vmware environment, should the external address become populated with the VM's (or hosts) ip address?



I have three clusters, and have found that only those using a "cloud provider" have external addresses when I run kubectl get nodes -o wide. It is my understanding that the "cloud provider" plugin (GCP, AWS, Vmware, etc) is what assigns the public ip address to the node.



KOPS deployed to GCP = external address is the real public IP addresses of the nodes.



Kubeadm deployed to vwmare, using vmware cloud provider = external address is the same as the internal address (a private range).



Kubeadm deployed, NO cloud provider = no external ip.



I ask because I have a tool that scrapes /api/v1/nodes and then interacts with each host that is finds, using the "external ip". This only works with my first two clusters.



My tool runs on the local network of the clusters, should it be targeting the "internal ip" instead? In other words, is the internal ip ALWAYS the IP address of the VM or physical host (when installed on bare metal).



Thank you










share|improve this question














In a vmware environment, should the external address become populated with the VM's (or hosts) ip address?



I have three clusters, and have found that only those using a "cloud provider" have external addresses when I run kubectl get nodes -o wide. It is my understanding that the "cloud provider" plugin (GCP, AWS, Vmware, etc) is what assigns the public ip address to the node.



KOPS deployed to GCP = external address is the real public IP addresses of the nodes.



Kubeadm deployed to vwmare, using vmware cloud provider = external address is the same as the internal address (a private range).



Kubeadm deployed, NO cloud provider = no external ip.



I ask because I have a tool that scrapes /api/v1/nodes and then interacts with each host that is finds, using the "external ip". This only works with my first two clusters.



My tool runs on the local network of the clusters, should it be targeting the "internal ip" instead? In other words, is the internal ip ALWAYS the IP address of the VM or physical host (when installed on bare metal).



Thank you







networking kubernetes






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 15:33









jsiriannijsirianni

183




183













  • It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

    – jsirianni
    Nov 15 '18 at 18:44



















  • It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

    – jsirianni
    Nov 15 '18 at 18:44

















It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

– jsirianni
Nov 15 '18 at 18:44





It appears that if I do not use a cloud provider, an externalIP will not be assigned to any nodes, per the last comment on this thread. stackoverflow.com/questions/40058795/…

– jsirianni
Nov 15 '18 at 18:44












1 Answer
1






active

oldest

votes


















0














Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.



When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.



https://github.com/google/metallb






share|improve this answer
























  • Thank you, this was what I was thinking but I needed to be sure.

    – jsirianni
    Nov 19 '18 at 15:02











  • Accepted answer but no up vote :)

    – adam wilhelm
    Jan 22 at 15:34











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%2f53322806%2fplease-example-kubernetes-external-address-vs-internal-addresses%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









0














Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.



When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.



https://github.com/google/metallb






share|improve this answer
























  • Thank you, this was what I was thinking but I needed to be sure.

    – jsirianni
    Nov 19 '18 at 15:02











  • Accepted answer but no up vote :)

    – adam wilhelm
    Jan 22 at 15:34
















0














Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.



When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.



https://github.com/google/metallb






share|improve this answer
























  • Thank you, this was what I was thinking but I needed to be sure.

    – jsirianni
    Nov 19 '18 at 15:02











  • Accepted answer but no up vote :)

    – adam wilhelm
    Jan 22 at 15:34














0












0








0







Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.



When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.



https://github.com/google/metallb






share|improve this answer













Baremetal will not have an "extrenal-IP" for the nodes and the "internal-ip" will be the IP address of the nodes. You are running your command from inside the same network for your local cluster so you should be able to use this internal IP address to access the nodes as required.



When using k8s on baremetal the external IP and loadbalancer functions don't natively exist. If you want to expose an "External IP", quotes because most cases it would still be a 10.X.X.X address, from your baremetal cluster you would need to install something like MetalLB.



https://github.com/google/metallb







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 '18 at 19:00









adam wilhelmadam wilhelm

513




513













  • Thank you, this was what I was thinking but I needed to be sure.

    – jsirianni
    Nov 19 '18 at 15:02











  • Accepted answer but no up vote :)

    – adam wilhelm
    Jan 22 at 15:34



















  • Thank you, this was what I was thinking but I needed to be sure.

    – jsirianni
    Nov 19 '18 at 15:02











  • Accepted answer but no up vote :)

    – adam wilhelm
    Jan 22 at 15:34

















Thank you, this was what I was thinking but I needed to be sure.

– jsirianni
Nov 19 '18 at 15:02





Thank you, this was what I was thinking but I needed to be sure.

– jsirianni
Nov 19 '18 at 15:02













Accepted answer but no up vote :)

– adam wilhelm
Jan 22 at 15:34





Accepted answer but no up vote :)

– adam wilhelm
Jan 22 at 15:34


















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%2f53322806%2fplease-example-kubernetes-external-address-vs-internal-addresses%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







這個網誌中的熱門文章

Hercules Kyvelos

Tangent Lines Diagram Along Smooth Curve

Yusuf al-Mu'taman ibn Hud