From dda44bf65968e55faeaf6da8a451018f710fed95 Mon Sep 17 00:00:00 2001 From: Nick Veitch Date: Mon, 22 Jan 2024 16:19:59 +0000 Subject: [PATCH] more 404s --- templates/kubernetes/docs/1.16/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.17/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.18/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.19/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.19/upgrading.md | 2 +- templates/kubernetes/docs/1.20/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.20/upgrading.md | 2 +- templates/kubernetes/docs/1.21/charm-docker-registry.md | 2 +- templates/kubernetes/docs/1.22/charm-docker-registry.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/templates/kubernetes/docs/1.16/charm-docker-registry.md b/templates/kubernetes/docs/1.16/charm-docker-registry.md index 9d79782cce5..c6b68c856f3 100644 --- a/templates/kubernetes/docs/1.16/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.16/charm-docker-registry.md @@ -485,7 +485,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.17/charm-docker-registry.md b/templates/kubernetes/docs/1.17/charm-docker-registry.md index 962df160cca..6f11f6c93ae 100644 --- a/templates/kubernetes/docs/1.17/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.17/charm-docker-registry.md @@ -485,7 +485,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.18/charm-docker-registry.md b/templates/kubernetes/docs/1.18/charm-docker-registry.md index 6dfeaeb2404..781deaff786 100644 --- a/templates/kubernetes/docs/1.18/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.18/charm-docker-registry.md @@ -486,7 +486,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.19/charm-docker-registry.md b/templates/kubernetes/docs/1.19/charm-docker-registry.md index 665388482cb..d7b6573a1c1 100644 --- a/templates/kubernetes/docs/1.19/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.19/charm-docker-registry.md @@ -486,7 +486,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.19/upgrading.md b/templates/kubernetes/docs/1.19/upgrading.md index 449ffc44f00..67d3f8f16ba 100644 --- a/templates/kubernetes/docs/1.19/upgrading.md +++ b/templates/kubernetes/docs/1.19/upgrading.md @@ -400,7 +400,7 @@ juju run-action kubernetes-worker/1 upgrade ## Upgrading the Machine's Series -All of the charms support [upgrading the machine's series via Juju](https://juju.is/docs/upgrading-series). +All of the charms support [upgrading the machine's series via Juju](https://juju.is/docs/juju/manage-machines#heading--upgrade-a-machine). As each machine is upgraded, the applications on that machine will be stopped and the unit will go into a `blocked` status until the upgrade is complete. For the worker units, pods will be drained from the node and onto one of the other nodes at the start of the upgrade, and the node will be removed diff --git a/templates/kubernetes/docs/1.20/charm-docker-registry.md b/templates/kubernetes/docs/1.20/charm-docker-registry.md index e0ef9306fb1..eb2ea297ece 100644 --- a/templates/kubernetes/docs/1.20/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.20/charm-docker-registry.md @@ -485,7 +485,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.20/upgrading.md b/templates/kubernetes/docs/1.20/upgrading.md index ad359ecdeb0..a9e74224461 100644 --- a/templates/kubernetes/docs/1.20/upgrading.md +++ b/templates/kubernetes/docs/1.20/upgrading.md @@ -414,7 +414,7 @@ juju run-action kubernetes-worker/1 upgrade ## Upgrading the Machine's Series -All of the charms support [upgrading the machine's series via Juju](https://juju.is/docs/upgrading-series). +All of the charms support [upgrading the machine's series via Juju](https://juju.is/docs/juju/manage-machines#heading--upgrade-a-machine). As each machine is upgraded, the applications on that machine will be stopped and the unit will go into a `blocked` status until the upgrade is complete. For the worker units, pods will be drained from the node and onto one of the other nodes at the start of the upgrade, and the node will be removed diff --git a/templates/kubernetes/docs/1.21/charm-docker-registry.md b/templates/kubernetes/docs/1.21/charm-docker-registry.md index 8d8bd66883b..57c0f9b48a7 100644 --- a/templates/kubernetes/docs/1.21/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.21/charm-docker-registry.md @@ -485,7 +485,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash diff --git a/templates/kubernetes/docs/1.22/charm-docker-registry.md b/templates/kubernetes/docs/1.22/charm-docker-registry.md index c575b243a61..1f8c72113f2 100644 --- a/templates/kubernetes/docs/1.22/charm-docker-registry.md +++ b/templates/kubernetes/docs/1.22/charm-docker-registry.md @@ -485,7 +485,7 @@ juju config docker-registry \ The recommended way to delete images from the registry is to use the `rmi` action. If necessary, this charm can be configured to -[allow deletion][storage-delete] of blobs and manifests by digest by setting +allow deletion of blobs and manifests by digest by setting the `storage-delete` config option to `true`: ```bash