Kubernetes cluster ip not answering Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Come Celebrate our 10 Year Anniversary!Kubernetes stuck on ContainerCreatingKubernetes cluster downproper shutdown of a kubernetes clusterKubernetes cluster change ipKubernetes : Inter-cluster networkingEquivalent to 'top' command on an EMR cluster?kubernetes - setting up a public available clusterCan you run a kubernetes cluster inside a kubernetes cluster?Elasticsearch - Kubernetes [handshake failed, mismatched cluster name]AWS kubernetes load balancer terminate SSL on port 443 and forward to service on port 80
Crossing US/Canada Border for less than 24 hours
How to report t statistic from R
What does Turing mean by this statement?
What are the discoveries that have been possible with the rejection of positivism?
Do I really need to have a message in a novel to appeal to readers?
How does light 'choose' between wave and particle behaviour?
Strange behavior of Object.defineProperty() in JavaScript
Would it be easier to apply for a UK visa if there is a host family to sponsor for you in going there?
Why are my pictures showing a dark band on one edge?
Is there public access to the Meteor Crater in Arizona?
Can the Flaming Sphere spell be rammed into multiple Tiny creatures that are in the same 5-foot square?
Did any compiler fully use 80-bit floating point?
How many morphisms from 1 to 1+1 can there be?
How does Belgium enforce obligatory attendance in elections?
Amount of permutations on an NxNxN Rubik's Cube
What makes a man succeed?
How can I prevent/balance waiting and turtling as a response to cooldown mechanics
What's the point of the test set?
In musical terms, what properties are varied by the human voice to produce different words / syllables?
What does 丫 mean? 丫是什么意思？
Maximum summed subsequences with non-adjacent items
Is CEO the "profession" with the most psychopaths?
AppleTVs create a chatty alternate WiFi network
What would you call this weird metallic apparatus that allows you to lift people?
Kubernetes cluster ip not answering
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Kubernetes stuck on ContainerCreatingKubernetes cluster downproper shutdown of a kubernetes clusterKubernetes cluster change ipKubernetes : Inter-cluster networkingEquivalent to 'top' command on an EMR cluster?kubernetes - setting up a public available clusterCan you run a kubernetes cluster inside a kubernetes cluster?Elasticsearch - Kubernetes [handshake failed, mismatched cluster name]AWS kubernetes load balancer terminate SSL on port 443 and forward to service on port 80
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
We've setup a kubernetes cluster with 3 masters and 3 workernodes. Then we've installed the kubernetes-dashboard which failes because it can't connect to kubernetes (api-server). It's looking for localhost:8080 but it's not reachable.
When executing env in a busybox I receive:
KUBERNETES_SERVICE_PORT_HTTPS=443
KUBERNETES_PORT=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_ADDR=10.2.0.1
KUBERNETES_SERVICE_HOST=10.2.0.1
KUBERNETES_SERVICE_PORT=443
So I would expect that kubernetes should be available on 10.2.0.1:443 but it doesn't answer. (Connection refused)
The bind-address is 0.0.0.0 (which is secured by ssl auth) the insecure-bind-address is unset (which means it's bound to 127.0.0.1).
Within the documentations I can see that the unsecured port (8080) is exposed to the cluster-network. But I can't see it. If I execute kubectl get services I see:
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes 10.2.0.1 <none> 443/TCP 1d
Do I have to take some more actions to expose 8080 there and/or make kubernetes available on these ports?
cluster service kubernetes
asked Jun 14 '16 at 13:25
memememe
112
add a comment |
We've setup a kubernetes cluster with 3 masters and 3 workernodes. Then we've installed the kubernetes-dashboard which failes because it can't connect to kubernetes (api-server). It's looking for localhost:8080 but it's not reachable.
When executing env in a busybox I receive:
KUBERNETES_SERVICE_PORT_HTTPS=443
KUBERNETES_PORT=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_ADDR=10.2.0.1
KUBERNETES_SERVICE_HOST=10.2.0.1
KUBERNETES_SERVICE_PORT=443
So I would expect that kubernetes should be available on 10.2.0.1:443 but it doesn't answer. (Connection refused)
The bind-address is 0.0.0.0 (which is secured by ssl auth) the insecure-bind-address is unset (which means it's bound to 127.0.0.1).
Within the documentations I can see that the unsecured port (8080) is exposed to the cluster-network. But I can't see it. If I execute kubectl get services I see:
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes 10.2.0.1 <none> 443/TCP 1d
Do I have to take some more actions to expose 8080 there and/or make kubernetes available on these ports?
cluster service kubernetes
asked Jun 14 '16 at 13:25
memememe
112
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41
add a comment |
We've setup a kubernetes cluster with 3 masters and 3 workernodes. Then we've installed the kubernetes-dashboard which failes because it can't connect to kubernetes (api-server). It's looking for localhost:8080 but it's not reachable.
When executing env in a busybox I receive:
KUBERNETES_SERVICE_PORT_HTTPS=443
KUBERNETES_PORT=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_ADDR=10.2.0.1
KUBERNETES_SERVICE_HOST=10.2.0.1
KUBERNETES_SERVICE_PORT=443
So I would expect that kubernetes should be available on 10.2.0.1:443 but it doesn't answer. (Connection refused)
The bind-address is 0.0.0.0 (which is secured by ssl auth) the insecure-bind-address is unset (which means it's bound to 127.0.0.1).
Within the documentations I can see that the unsecured port (8080) is exposed to the cluster-network. But I can't see it. If I execute kubectl get services I see:
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes 10.2.0.1 <none> 443/TCP 1d
Do I have to take some more actions to expose 8080 there and/or make kubernetes available on these ports?
cluster service kubernetes
asked Jun 14 '16 at 13:25
memememe
112
We've setup a kubernetes cluster with 3 masters and 3 workernodes. Then we've installed the kubernetes-dashboard which failes because it can't connect to kubernetes (api-server). It's looking for localhost:8080 but it's not reachable.
When executing env in a busybox I receive:
KUBERNETES_SERVICE_PORT_HTTPS=443
KUBERNETES_PORT=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP=tcp://10.2.0.1:443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_ADDR=10.2.0.1
KUBERNETES_SERVICE_HOST=10.2.0.1
KUBERNETES_SERVICE_PORT=443
So I would expect that kubernetes should be available on 10.2.0.1:443 but it doesn't answer. (Connection refused)
The bind-address is 0.0.0.0 (which is secured by ssl auth) the insecure-bind-address is unset (which means it's bound to 127.0.0.1).
Within the documentations I can see that the unsecured port (8080) is exposed to the cluster-network. But I can't see it. If I execute kubectl get services I see:
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes 10.2.0.1 <none> 443/TCP 1d
Do I have to take some more actions to expose 8080 there and/or make kubernetes available on these ports?
cluster service kubernetes
cluster service kubernetes
asked Jun 14 '16 at 13:25
memememe
112
asked Jun 14 '16 at 13:25
memememe
112
asked Jun 14 '16 at 13:25
memememe
112
asked Jun 14 '16 at 13:25
memememe
112
asked Jun 14 '16 at 13:25
memememe
112
112
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41
add a comment |
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41
add a comment |
2 Answers
2
active
oldest
votes
Connecting to localhost:8080 is the default behavior when a Kubernetes client isn't configured with a specific location of an apiserver. Typically, the dashboard connects to the apiserver using the "In cluster credentials" that are added to the pod via a service account.
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
add a comment |
This is the typical behaviour when root is used for kubectl and /etc/kubernetes/admin.conf is not in /root/.kube/config (you need to rename it).
The recommended procedure is to create a non-root user e.x(kubeadmin) and place /etc/kubernetes/admin.conf in /home/of/kubeadmin/.kube/config
[root@k8s-1 ~]# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@k8s-1 ~]# mkdir /root/.kube
[root@k8s-1 ~]# cp /etc/kubernetes/admin.conf /root/.kube/config
[root@k8s-1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-node1 Ready master 90d v1.12.3
k8s-node2 Ready <none> 90d v1.12.3
k8s-node3 Ready <none> 90d v1.12.3
k8s-node4 Ready <none> 6d1h v1.12.3
answered Mar 14 at 15:20
gixnexgixnex
464
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f783859%2fkubernetes-cluster-ip-not-answering%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Connecting to localhost:8080 is the default behavior when a Kubernetes client isn't configured with a specific location of an apiserver. Typically, the dashboard connects to the apiserver using the "In cluster credentials" that are added to the pod via a service account.
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
add a comment |
Connecting to localhost:8080 is the default behavior when a Kubernetes client isn't configured with a specific location of an apiserver. Typically, the dashboard connects to the apiserver using the "In cluster credentials" that are added to the pod via a service account.
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
add a comment |
Connecting to localhost:8080 is the default behavior when a Kubernetes client isn't configured with a specific location of an apiserver. Typically, the dashboard connects to the apiserver using the "In cluster credentials" that are added to the pod via a service account.
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
Connecting to localhost:8080 is the default behavior when a Kubernetes client isn't configured with a specific location of an apiserver. Typically, the dashboard connects to the apiserver using the "In cluster credentials" that are added to the pod via a service account.
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
answered Jun 15 '16 at 7:05
Robert BaileyRobert Bailey
44436
44436
add a comment |
add a comment |
This is the typical behaviour when root is used for kubectl and /etc/kubernetes/admin.conf is not in /root/.kube/config (you need to rename it).
The recommended procedure is to create a non-root user e.x(kubeadmin) and place /etc/kubernetes/admin.conf in /home/of/kubeadmin/.kube/config
[root@k8s-1 ~]# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@k8s-1 ~]# mkdir /root/.kube
[root@k8s-1 ~]# cp /etc/kubernetes/admin.conf /root/.kube/config
[root@k8s-1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-node1 Ready master 90d v1.12.3
k8s-node2 Ready <none> 90d v1.12.3
k8s-node3 Ready <none> 90d v1.12.3
k8s-node4 Ready <none> 6d1h v1.12.3
answered Mar 14 at 15:20
gixnexgixnex
464
add a comment |
This is the typical behaviour when root is used for kubectl and /etc/kubernetes/admin.conf is not in /root/.kube/config (you need to rename it).
The recommended procedure is to create a non-root user e.x(kubeadmin) and place /etc/kubernetes/admin.conf in /home/of/kubeadmin/.kube/config
[root@k8s-1 ~]# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@k8s-1 ~]# mkdir /root/.kube
[root@k8s-1 ~]# cp /etc/kubernetes/admin.conf /root/.kube/config
[root@k8s-1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-node1 Ready master 90d v1.12.3
k8s-node2 Ready <none> 90d v1.12.3
k8s-node3 Ready <none> 90d v1.12.3
k8s-node4 Ready <none> 6d1h v1.12.3
answered Mar 14 at 15:20
gixnexgixnex
464
add a comment |
This is the typical behaviour when root is used for kubectl and /etc/kubernetes/admin.conf is not in /root/.kube/config (you need to rename it).
The recommended procedure is to create a non-root user e.x(kubeadmin) and place /etc/kubernetes/admin.conf in /home/of/kubeadmin/.kube/config
[root@k8s-1 ~]# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@k8s-1 ~]# mkdir /root/.kube
[root@k8s-1 ~]# cp /etc/kubernetes/admin.conf /root/.kube/config
[root@k8s-1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-node1 Ready master 90d v1.12.3
k8s-node2 Ready <none> 90d v1.12.3
k8s-node3 Ready <none> 90d v1.12.3
k8s-node4 Ready <none> 6d1h v1.12.3
answered Mar 14 at 15:20
gixnexgixnex
464
This is the typical behaviour when root is used for kubectl and /etc/kubernetes/admin.conf is not in /root/.kube/config (you need to rename it).
The recommended procedure is to create a non-root user e.x(kubeadmin) and place /etc/kubernetes/admin.conf in /home/of/kubeadmin/.kube/config
[root@k8s-1 ~]# kubectl get nodes
The connection to the server localhost:8080 was refused - did you specify the right host or port?
[root@k8s-1 ~]# mkdir /root/.kube
[root@k8s-1 ~]# cp /etc/kubernetes/admin.conf /root/.kube/config
[root@k8s-1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-node1 Ready master 90d v1.12.3
k8s-node2 Ready <none> 90d v1.12.3
k8s-node3 Ready <none> 90d v1.12.3
k8s-node4 Ready <none> 6d1h v1.12.3
answered Mar 14 at 15:20
gixnexgixnex
464
edited Mar 14 at 15:25
answered Mar 14 at 15:20
gixnexgixnex
464
answered Mar 14 at 15:20
gixnexgixnex
464
answered Mar 14 at 15:20
gixnexgixnex
464
464
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f783859%2fkubernetes-cluster-ip-not-answering%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
As far it relates to the availability of the 443 port it's solved. The setup runs in a vm and has a little different ip configuration (public ip a which is mapped to ip b on the interface). After setting the --advertise-address to the public ip a I can connect to 443 and it answers as expected. But I need the port 8080 to be available in the cluster.
– meme
Jun 14 '16 at 13:41