Provide the instruction for air-gapped install environment

[valumar]

The docs should contain the instruction of how AI can be used to deploy Openshift in air-gapped environment with local docker registry and local iso-repos

[kenmoini]

ker-bump

I've gotten most things working in a disconnected fashion but for some reason the PULL_SECRET provided in the onprem-environment env var file is not being accepted by the OAS API container...getting the following error

FATA[0000]/go/src/github.com/openshift/origin/cmd/main.go:193 main.main.func1() failed to create pull secret validator        error="invalid reference format"

My WIP script is found here: https://github.com/kenmoini/oas-disconnected/blob/main/disconnected-oas.unified.bootstrap.sh

Anyone got any idea on how to include the PULL_SECRET so that the OAS API is happy with it? That's pretty much the only thing holding back this offline deployment...

[kenmoini]

Well, I got it working:

Seems to be that when you specify the images there's some odd condition that checks pull secrets and yada yada...not defining the different _IMAGE vars in the onprem-environment file makes it all work just fine.

I'll be splitting out that unified bootstrap script and documenting the processes to work for low/high side air-gapped networks sometime over the next few days.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[valumar]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[valumar]

/lifecycle frozen

[valumar]

/remove-lifecycle stale

[valumar]

up

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale