Kuberneted dashboard is not accessible after deploying 3 node cluster

0 votes

Note: About my cluster setup

I am using Vbox with Centos 8 image.

It is 3 node cluster

----------------------------------------------

Network setup of vbox for VM mention as following which i am using.

Master:   1 NAT Card,   2-  Bridge Adaptor

node1-    1 NAT Card,   2-  Bridge Adaptor

node2-    1 NAT Card,   2-  Bridge Adaptor

-----------------------------------------------

Problem:

I want to deploy kubernetes cluster with self sign CA. To use cert-manager

default CA created by kubeadm command during cluster initialization its not working properly.

I am facing issue when i deploying cluster with default CA created by kubeadm. After deploying network and dashboard i am not able to

open dashboard in my chrome browser because its complaining CA is not secure and not signed.

Please share any link or docs where explain how to deploy kubernetes cluster with self sign cert.

Jul 11, 2020 in Kubernetes by anonymous
• 180 points
637 views

1 answer to this question.

0 votes

Hi,

There may a problem with firewalld. You need to disable your firewall permanently. There are some programs that the firewall will not allow.

answered Jul 13, 2020 by MD
• 95,460 points

Related Questions In Kubernetes

0 votes
1 answer
–1 vote
1 answer

order to apply kubernetes-dashboard ? before I join the worker nodes or after the join of the worker node ?

Not really. There are a few things ...READ MORE

answered Mar 18, 2019 in Kubernetes by Vardhan
• 13,150 points
1,277 views
0 votes
1 answer
0 votes
0 answers

Kubernetes dashboard Url is not accessing in my browser?

im facing the issue from yesterday.  i ...READ MORE

Jun 20, 2019 in Kubernetes by anonymous

closed Jun 20, 2019 by Kalgi 1,131 views
+1 vote
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17, 2019 in Others by anonymous
15,476 views
0 votes
1 answer

permissions related to AWS ECR

if you add allowContainerRegistry: true, kops will add those permissions ...READ MORE

answered Oct 9, 2018 in Kubernetes by Kalgi
• 52,350 points
1,396 views
0 votes
1 answer

Error getting primary cp: could not find master node, minikube is exiting due to an error

Hi@akhtar, You may receive this error when you ...READ MORE

answered May 19, 2020 in Kubernetes by MD
• 95,460 points
1,005 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP