Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide the instruction for air-gapped install environment #2847

Open
valumar opened this issue Nov 1, 2021 · 11 comments
Open

Provide the instruction for air-gapped install environment #2847

valumar opened this issue Nov 1, 2021 · 11 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@valumar
Copy link

valumar commented Nov 1, 2021

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
@valumar valumar changed the title Provide the instruction for air-gaped install environment Provide the instruction for air-gapped install environment Nov 3, 2021
@kenmoini
Copy link
Contributor

kenmoini commented Jan 1, 2022

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
Copy link
Contributor

kenmoini commented Jan 1, 2022

Well, I got it working:
image

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
Copy link
Contributor

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2022
@valumar
Copy link
Author

valumar commented Apr 1, 2022

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2022
@openshift-bot
Copy link
Contributor

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 30, 2022
@valumar
Copy link
Author

valumar commented Jun 30, 2022

/lifecycle frozen

@valumar
Copy link
Author

valumar commented Jun 30, 2022

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 30, 2022
@valumar
Copy link
Author

valumar commented Jul 26, 2022

up

@openshift-bot
Copy link
Contributor

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2022
@valumar
Copy link
Author

valumar commented Oct 31, 2022

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2022
@valumar
Copy link
Author

valumar commented Oct 31, 2022

/lifecycle frozen

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@openshift-bot @kenmoini @valumar