-
Notifications
You must be signed in to change notification settings - Fork 1.8k
RHDEVDOCS-6206: Builds for OpenShift: Disconnected Install Instructions #85106
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.
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
Merged
mburke5678
merged 1 commit into
openshift:build-docs-main
from
shivanisathe25:network-restricted-env
Nov 26, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26 changes: 26 additions & 0 deletions
26
modules/ob-creating-buildah-build-in-a-network-restricted-environment.adoc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
// Module included in the following assemblies: | ||
// | ||
//* builds/work-with-builds.adoc | ||
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id='ob-creating-buildah-build-in-a-network-restricted-environment_{context}'] | ||
= Creating buildah build in a network restricted environment | ||
|
||
You can create a `buildah` build in a network restricted environment by mirroring the images required by the `buildah` build strategy. | ||
|
||
.Prerequisites | ||
|
||
* Your cluster can connect and interact with the git source that you can use to create the buildah build. | ||
.Procedure | ||
|
||
. Run the following command to mirror the images required by the `buildah` build strategy: | ||
+ | ||
[source,terminal] | ||
---- | ||
$ oc image mirror --insecure -a <registry_authentication> registry.redhat.io/ubi8/buildah@sha256:1c89cc3cab0ac0fc7387c1fe5e63443468219aab6fd531c8dad6d22fd999819e <mirror_registry>/<repo>/ubi8_buildah | ||
---- | ||
+ | ||
. Perform the steps mentioned in the "Creating a buildah build" section. | ||
|
26 changes: 26 additions & 0 deletions
26
modules/ob-creating-s2i-build-in-a-network-restricted-environment.adoc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// * builds/work-with-builds.adoc | ||
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id='ob-creating-source-to-image-build-in-a-network-restricted-environment_{context}'] | ||
= Creating source-to-image build in a network restricted environment | ||
|
||
You can create a `source-to-image` build in a network restricted environment by mirroring the images required by the `source-to-image` build strategy. | ||
|
||
.Prerequisites | ||
|
||
* Your cluster can connect and interact with the git source that you can use to create the source-to-image build. | ||
* You have the builder-image required to create the `source-to-image` build in your local registry. If you do not have the builder-image in the local registry, mirror the source image. | ||
|
||
.Procedure | ||
|
||
. Run the following command to mirror the images required by the `source-to-image` build strategy: | ||
+ | ||
[source,terminal] | ||
---- | ||
$ oc image mirror --insecure -a <registry_authentication> registry.redhat.io/source-to-image/source-to-image-rhel8@sha256:d041c1bbe503d152d0759598f79802e257816d674b342670ef61c6f9e6d401c5 <mirror_registry>/<repo>/source-to-image-source-to-image-rhel8 | ||
---- | ||
+ | ||
|
||
. Perform the steps mentioned in the "Creating a source-to-image build" section. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be restricted network? I see network restricted environment is used elsewhere in the Builds docs.
If network restricted environment and restricted network are not the same thing, we should at least go with network-restricted environment.
Can be done in a separate PR. Not worth holding up the merge.