search

ibm-cloud-architecture / terraform-openshift4-aws

OpenShift 4 installation automation asset
Apache License 2.0
84 stars 114 forks source link

Is it even a complete solution? #40

Closed abhi-vaidya closed 3 years ago

abhi-vaidya commented 3 years ago

1st Creating interface endpoint creates dns issue if terraform destroy needs to be executed. 2nd It does not create worker node. only master and bootstrap. 3rd, master nodes does not come up healthy status in elb. Even there is no way to ssh in to server as scripts does not save ssh keys. so no chance to debug.

So, just want to confirm if its it is a complete solution or work in progress. Also if there are work arounds to above issues, please update readme.

vbudi000 commented 3 years ago
  1. I have not seen a problem as long as the environment destroy is following the readme and the deployment is actually successful
  2. worker nodes are created by the cluster once the master nodes are up, not by terraform, hence the destroy process requires additional steps
  3. if master nodes never become healthy, check the procedure - are you using disconnected etc?