You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dc96ecf
Browse filesBrowse the repository at this point in the historyBrowse files
docs(air-gapped): address review comments for registry mirrors
- Fix containerd auth example: replace unsupported [host.*.auth] block
with header-based Basic Auth per official hosts.toml format
- Highlight global vs per-cluster secret precedence with warning block
Assisted-By: Claude AI
Signed-off-by: Kirill Ilin <[email protected]>
The `patch-containerd` secret from the `cozy-system` namespace is automatically copied
@@ -356,9 +366,9 @@ instead of using the global `patch-containerd` secret:
356
366
- The tenant cluster must be deployed with a Kubernetes package version 0.23.1 or later, which is available since Cozystack 0.32.1.
357
367
- Before deploying the tenant cluster, create a Kubernetes Secret named `kubernetes-<cluster-name>-patch-containerd` in the tenant cluster namespace, using the same format as the examples above.
358
368
359
-
If both the global `patch-containerd` secret and a per-cluster secret exist,
360
-
the global secret is used. To use per-cluster configuration only,
361
-
do not create the global `patch-containerd` secret in `cozy-system`.
369
+
{{% alert color="warning" %}}
370
+
**Important:** If both the global `patch-containerd` secret and a per-cluster secret exist, the global secret takes precedence and the per-cluster secret is ignored. To use a per-cluster configuration, ensure that the global `patch-containerd` secret in the `cozy-system` namespace is not present.
371
+
{{% /alert %}}
362
372
363
373
To learn more about registry configuration values, read the [CRI Plugin configuration guide](
0 commit comments