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

[enterprise-4.12] RHDEVDOCS-2587 Bug 1810904 - [DOC]Should document how to configure pu… #49652

Merged
merged 1 commit into from
Aug 26, 2022
Merged

[enterprise-4.12] RHDEVDOCS-2587 Bug 1810904 - [DOC]Should document how to configure pu… #49652

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 10 additions & 9 deletions modules/builds-image-source.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
//
// * builds/creating-build-inputs.adoc

:_content-type: CONCEPT

[id="builds-image-source_{context}"]
= Image source

Expand Down Expand Up @@ -46,7 +48,9 @@ source:
If your cluster uses an `ImageContentSourcePolicy` object to configure repository mirroring, you can use only global pull secrets for mirrored registries. You cannot add a pull secret to a project.
====

Optionally, if an input image requires a pull secret, you can link the pull secret to the service account used by the build. By default, builds use the `builder` service account. The pull secret is automatically added to the build if the secret contains a credential that matches the repository hosting the input image. To link a pull secret to the service account used by the build, run:
.Images that require pull secrets

When using an input image that requires a pull secret, you can link the pull secret to the service account used by the build. By default, builds use the `builder` service account. The pull secret is automatically added to the build if the secret contains a credential that matches the repository hosting the input image. To link a pull secret to the service account used by the build, run:

[source,terminal]
----
Expand All @@ -60,12 +64,9 @@ This feature is not supported for builds using the custom strategy.
====
endif::[]

/////
[role="_additional-resources"]
.Additional resources
.Images on mirrored registries that require pull secrets

* Custom Strategy
ifndef::openshift-online[]
* ImageStreamTags
endif::[]
/////
When using an input image from a mirrored registry, if you get a `build error: failed to pull image` message, you can resolve the error by using either of the following methods:

* Create an input secret that contains the authentication credentials for the builder image’s repository and all known mirrors. In this case, create a pull secret for credentials to the image registry and its mirrors.
* Use the input secret as the pull secret on the `BuildConfig` object.