Skip to content

docs(exapp-operations): registry mappings on Kubernetes daemons - #11

Merged
oleksandr-nc merged 1 commit into
mainfrom
docs/k8s-registry-mappings
Sep 25, 2026
Merged

oleksandr-nc merged 1 commit into
mainfrom
docs/k8s-registry-mappings

Conversation

@oleksandr-nc

Copy link
Copy Markdown
Collaborator

The guides say that daemon registry mappings and the local target are Docker-only and that a Kubernetes daemon always pulls from an in-cluster registry. nextcloud/app_api#1046 makes the Kubernetes backend apply the mappings, and with nextcloud/HaRP#122 a local mapping sets imagePullPolicy: Never, so those passages are wrong once that lands.

Changes

  • kubernetes.md: how mirrored and air-gapped registries work on a Kubernetes daemon, what local means there depending on the HaRP version, and that an authenticated registry needs imagePullSecrets on the namespace's ServiceAccount because HaRP sets none.
  • exapp-ai-maintenance.md: the Kubernetes exclusion now says why the runbook does not apply as written and what to do instead.
  • operations.md: the registry mapping entry covers both backends and the stored form of the values.

Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
@oleksandr-nc
oleksandr-nc force-pushed the docs/k8s-registry-mappings branch from 499cf11 to a4ecca0 Compare September 25, 2026 10:39
@oleksandr-nc
oleksandr-nc merged commit 2446235 into main Sep 25, 2026
4 checks passed
@oleksandr-nc
oleksandr-nc deleted the docs/k8s-registry-mappings branch September 25, 2026 10:41
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