feat: added snc flag to disable cluster readiness.

[adrianriobo]

Fix #631.

[anjannath]

with the --disable-cluster-readiness flag also its printing the following, would be good to print another message saying kubeconfig needs to be fetched manually from the instance?

DEBU error getting main-aosKubeconfig
Cluster has been started you can access console at: https://console-openshift-console.apps.3.21.30.109.nip.io.

[wes-spinks]

Sorry for the delay on following up here @adrianriobo - I've used this flag a few dozen times and it is very helpful for my CI flow! I do agree with above, a message to the user to get kubeconfig makes sense.

Though, I'm wondering, is there another way to get SSH key to connect to the new host without --debug? If not then should setting this --disable-cluster-readiness flag suggest --debug? I think some secrets are pushed to SSM, but if I'm given an AWS account (with limited IAM roles) will I be able to easily retrieve these creds?

[anjannath]

Though, I'm wondering, is there another way to get SSH key to connect to the new host without --debug?

iirc, the o/p are still written to the outputs directory at the end (--conn-details-output) and it contains the ssh key

[anjannath]

we can address #699 (comment) in a follow up PR later, would be get this in!