Passwordless communication require on every container run for installer container

[virendra-sharma]

This is observed that we need to do passwordless communication between installer container and each node of cluster, on every new container run of installer.

Usecase

If we have 10 node cluster and using container installer, we need to do passwordless communication between them and it will communicate flowless for particular container installer only.
In scenario of creating new installer container, need to follow same process again and again for all 10 nodes of cluster, which will be time consuming and not efficient way.

[farhan7500]

This will only be required in case the container is deleted/removed. Why are we removing the container? You can reuse the same container (which will have all the necessary changes you've made in the previous run) by just execution its shell whenever required.

You don't have to spawn a new container out of the image every time.

[virendra-sharma]

As per user front, node which holds installer container is not part of cluster so customer won't be holding that machine just for installer container only. What if that machine wiped off and used for some other purpose after cleanup??

[farhan7500]

The ansible controller should never be the part of the cluster. Cnntainer or VM or bare metal, if the controller OS is wiped out, all information will be lost.

[virendra-sharma]

@prablr79 Please consider my usecase and suggest.

[prablr79]

This can be consider as enhacement, we can do a debate on this usecase.