Hi. > I suspect this is in the context of OCP 4.x ? > Yes it is, we are traying install RHCOS on bare metal and after we will install openshift 4.x.
We would like inject the ignition files (with ssh key, etc) inside iso image to avoid manual steps. we know that is possible in CoreOS here <https://github.com/coreos/coreos-installer#install-with-cargo> is explain how to do. Do you know a workaround for this problem? Best regards Sérgio Daniel Comnea <comnea.d...@gmail.com> escreveu no dia quarta, 11/12/2019 à(s) 16:54: > I suspect this is in the context of OCP 4.x ? If so, my understanding is > that on OCP 4.x deployment this won't be possible as RHCOS is *just* > another component and so it comes bundled with the whole release payload. > If guess it might be a dev way to inject different images but not sure if > that is a good idea for running in a prod environment > > On Wed, Dec 11, 2019 at 2:57 PM Sérgio Cascão <smrcas...@gmail.com> wrote: > >> Hi. >> I would like to know if is it possible to customize an iso RHcos with >> ignition files inside. this is to install in bare metal and avoid insert >> manual steps. I know the coreos-installer and I already have inserted an >> ignition file inside coreOS image. >> My question is there some way to insert an ignition file inside RHCOS >> images >> <https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.2/latest/> >> ? >> If is it possible how? >> Best regards. >> Sérgio >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
