Skip to content

Document that same-project images still need a pull secret #78

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

Merged
acoshift merged 1 commit into from
Oct 28, 2026
Merged

Document that same-project images still need a pull secret #78

Show file tree
Hide file tree
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
12 changes: 6 additions & 6 deletions content/registry/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: 'Registry overview'
linkTitle: 'Overview'
weight: 1
description: 'A private container registry at registry.deploys.app, one namespace per project.'
lead: 'Every project gets a private slice of registry.deploys.app for its own application images. Push from CI, pull from your deployments — no extra credentials to plumb around.'
lead: 'Every project gets a private slice of registry.deploys.app for its own application images. Push from CI. A deployment in the same project still needs a pull secret to pull them.'
---

## The Registry page
Expand Down Expand Up @@ -93,15 +93,15 @@ repository implicitly. There's no separate "create repository" step.

## Pulling from a deployment

Deployments in the same project pull from `registry.deploys.app` automatically
— the platform injects the right credentials at deploy time. You set
`image: registry.deploys.app/<project>/<name>:<tag>` in the deploy config and
that's it.
A same-project image still needs a pull secret. On the deploy form, New creates
the registry-pull account and secret for the selected location. Set the image
and select that secret:

```json
{
"name": "api",
"image": "registry.deploys.app/acme/api:v1.8.0"
"image": "registry.deploys.app/acme/api:v1.8.0",
"pullSecret": "registry-pull"
}
```

Expand Down
3 changes: 2 additions & 1 deletion content/registry/pull-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,8 @@ lead: 'A pull secret holds the credentials a deployment uses to pull an image fr
Three cases:

- Image in **`registry.deploys.app/<project>/...`** within the *same* project →
no pull secret needed.
a pull secret is still required. On the deploy form, New creates the
registry-pull account and secret for the selected location.
- Image in `registry.deploys.app/<otherProject>/...` → create a pull secret
with credentials that have read access to that project's registry.
- Image in a **third-party registry** (Docker Hub private, GHCR, GCR, ECR,
Expand Down
Loading