Skip to content

feat: use cluster-wide indev pull secrets for private registries#6

Merged
Alfred Tovsen Mo (alfredtm) merged 1 commit into
mainfrom
feat/global-pull-secret
Jun 10, 2026
Merged

feat: use cluster-wide indev pull secrets for private registries#6
Alfred Tovsen Mo (alfredtm) merged 1 commit into
mainfrom
feat/global-pull-secret

Conversation

@alfredtm

Copy link
Copy Markdown
Contributor

indev v1.4.0 shipped pullsecret management, which collapses the private-registry experience to one question, asked once per cluster:

indev pullsecret create --name ghcr --registry ghcr.io:<user>:<token>
indev cluster pullsecret set <cluster> ghcr

Changes

  • deploy-app: private-registry section now checks indev pullsecret list first, reuses/extends an existing secret, or creates + assigns one. The old per-namespace oc create secret docker-registry flow and imagePullSecrets pod-spec wiring are gone. Bash(oc create*) dropped from allowed-tools; scoped indev pullsecret/indev cluster pullsecret added.
  • ghcr.io guidance (our users' default registry): username = GitHub username, token = classic PAT with read:packages — fine-grained tokens and passwords don't work with ghcr. Triage table also covers the expired-PAT → ImagePullBackOff case.
  • manifest-templates: manifests are now identical for public and private images.
  • README: notes the indev v1.4+ requirement.

🤖 Generated with Claude Code

indev v1.4 added pullsecret management. deploy-app now sets up pull
credentials once per cluster (indev pullsecret create + indev cluster
pullsecret set) instead of per-namespace docker-registry secrets, and
manifests no longer carry imagePullSecrets. Includes ghcr.io guidance:
classic PAT with read:packages, not a password or fine-grained token.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@alfredtm Alfred Tovsen Mo (alfredtm) merged commit f7142ef into main Jun 10, 2026
3 checks passed
@alfredtm Alfred Tovsen Mo (alfredtm) deleted the feat/global-pull-secret branch June 10, 2026 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant