Highlighted
Mission Specialist
Mission Specialist
  • 819 Views

OpenShift 4 Installation - Deployment Topology

Hi,

I have installed OpenShift 4.0 today on AWS (per the trial url). I could see this has Installed 16 odd nodes. Could not figure out the deployment topology created.

Would appreciate if someone can help me understand this.

Many Thanks,
Sachin

0 Kudos
4 Replies
Moderator
Moderator
  • 815 Views

Re: OpenShift 4 Installation - Deployment Topology

Can you post a copy of your install-config.yaml. The default config is a 6 node cluster - 3 masters and 3 worker nodes. There will be one bootstrap node that runs for a few minutes and is then terminated. 

0 Kudos
Reply
Loading...
Highlighted
Mission Specialist
Mission Specialist
  • 804 Views

Re: OpenShift 4 Installation - Deployment Topology

Hi Srinivas,

Thanks for the quick response. I am trying to sort this out. To me it looks like since the installer ran multiple times (with different cluster names) so result in multiple nodes. The Cluster destroy script did not clean up properly. Let me check these things and come back.

However, apart from this, if you could help me with the following:

1. I see these nodes are created with a different key and I don't have this key. Does it mean that we can't login to these nodes?

2. Is there any concept of bastion host like 3.x ?

Many Thanks,
sachin

 

0 Kudos
Reply
Loading...
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 737 Views

Re: OpenShift 4 Installation - Deployment Topology

Hi Sachin,

Did you figure out what caused your cluster to have 16 nodes ? It seems to me that you must have ran cluster installation few times or delete/cleanup didn't work.

Cheers !!
Vijay
0 Kudos
Reply
Loading...
Highlighted
Mission Specialist
Mission Specialist
  • 704 Views

Re: OpenShift 4 Installation - Deployment Topology

Hi Vijay, Yes, there was a problem with the cleanup. Now I see only 6 nodes only. It perfectly looks okay now.

 

Thanks,

Sachin

Reply
Loading...
Join the discussion
You must log in to join this conversation.