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

docs: update incorrect createPullSecrets reference #2750

Merged
merged 1 commit into from
Nov 2, 2023
Merged

docs: update incorrect createPullSecrets reference #2750

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/configuration/images/pull.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ In many cases, DevSpace automatically creates pull secrets for you but you can a
DevSpace can automatically create pull secrets to provide registry credentials for Kubernetes to pull images from these private registries. DevSpace retrieves the credentials from your local credentials store in Docker.

The following functions can be called in the scripts defined in your `pipelines` section and when DevSpace executes them, it triggers pull secrets to be created:
1. `build_images` (unless `createPullSecrets` is `false` for the respective image in the `images` section of `devspace.yaml`)
1. `build_images` (unless [`createPullSecret`](../images#images-createPullSecret) is `false` for the respective image)
2. `ensure_pull_secrets`

### Manual
Expand Down