Merge ~valentinviennot/ubuntu-docker-images:deprecate-21.10 into ~ubuntu-docker-images/ubuntu-docker-images/+git/templates:main

[Valentin Viennot]

- Deprecate the 21.10 tracks
- Clarify channels description
- Includes https://code.launchpad.net/~sergiodj/ubuntu-docker-images/+git/templates/+ref/fix-repo-ownership-name
- Generate new data

[Sergio Durigan Junior (sergiodj)]

Thanks, Valentin.

LGTM, +1.

review: Approve

Unmerged commits

120990e... by Valentin Viennot on 2022-09-06

generate new data

Signed-off-by: Valentin Viennot <email address hidden>

21c0cd4... by Valentin Viennot on 2022-09-06

update template to clarify

Signed-off-by: Valentin Viennot <email address hidden>

4632226... by Valentin Viennot on 2022-04-19

Update data to deprecate 21.10

Signed-off-by: Valentin Viennot <email address hidden>

cbdaf72... by Sergio Durigan Junior on 2022-09-01

Fix URLs of git repositories (ownership changed)

The ownership of the git repos for the ubuntu-docker-images project
has recently changed, so we have to adjust the URLs here as well.

Signed-off-by: Sergio Durigan Junior <email address hidden>

diff --git a/data/apache2.yaml b/data/apache2.yaml
index 2f8133c..283a035 100644
--- a/data/apache2.yaml
+++ b/data/apache2.yaml
@@ -16,6 +16,11 @@ releases:
     risk: beta
     version: '2.4.48'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '2.4'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -61,7 +66,7 @@ parameters:
     description: Mount and serve a local website.
   - type: -v
     value: /path/to/apache2.conf:/etc/apache2/apache2.conf
-    description: Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)).
+    description: Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)).
 debug:
   - nothing
 microk8s:
@@ -69,10 +74,10 @@ microk8s:
     files:
       - key: apache2
         name: apache2.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04
       - key: apache2-site
         name: index.html
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04
     access: You will now be able to connect to the apache2 server on `http://localhost:30080`.
diff --git a/data/bind9.yaml b/data/bind9.yaml
index 4a52e08..985db2d 100644
--- a/data/bind9.yaml
+++ b/data/bind9.yaml
@@ -18,6 +18,11 @@ releases:
     risk: beta
     version: '9.16.15'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '9.18'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -49,7 +54,7 @@ parameters:
     description: The user which will start the `named` process.
   - type: -v
     value: /path/to/bind/configuration:/etc/bind/named.conf
-    description: Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)).
+    description: Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)).
   - type: -v
     value: /path/to/cached/data:/var/cache/bind
     description: Location where locally cached data can be dumped.
@@ -60,5 +65,5 @@ debug:
   - nothing
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04
     access: You will now be able to connect to the Bind9 server on localhost:30053`.
diff --git a/data/cassandra.yaml b/data/cassandra.yaml
index 48d9da3..452bf8f 100644
--- a/data/cassandra.yaml
+++ b/data/cassandra.yaml
@@ -91,5 +91,5 @@ debug:
   - nothing
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04
     access: You can now access the cassandra server on port 9042 (e.g., cqlsh localhost 9042)
diff --git a/data/cortex.yaml b/data/cortex.yaml
index e6aa434..0689a72 100644
--- a/data/cortex.yaml
+++ b/data/cortex.yaml
@@ -73,7 +73,7 @@ parameters:
     description: Expose Cortex on `localhost:32709`.
   - type: -v
     value: /my/local/cortex.yaml:/etc/cortex/cortex.yaml
-    description: Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)).
+    description: Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)).
 debug:
   - nothing
 microk8s:
@@ -81,7 +81,7 @@ microk8s:
     files:
       - key: main-config
         name: cortex.yaml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04
     access: You will now be able to connect to the Cortex server on `localhost:32709`.
diff --git a/data/grafana.yaml b/data/grafana.yaml
index d000148..227d7e9 100644
--- a/data/grafana.yaml
+++ b/data/grafana.yaml
@@ -74,16 +74,16 @@ parameters:
 debug: None
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04
     access: You will now be able to connect to the Grafana on `http://localhost:30000`.
   configmap:
     files:
     - key: grafana-datasource
       name: datasource.yml
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04
+      link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04
     - key: grafana-dashboard-definition
       name: dashboard.yml
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04
+      link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04
     - key: grafana-dashboard
       name: system-stats-dashboard.json
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04
+      link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04
diff --git a/data/kafka.yaml b/data/kafka.yaml
index c995b23..9cddd71 100644
--- a/data/kafka.yaml
+++ b/data/kafka.yaml
@@ -44,5 +44,5 @@ debug:
   - nothing
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04
     access: Apache Kafka will be available on the K8s cluster as a `kafka-service` Service.
diff --git a/data/loki.yaml b/data/loki.yaml
index e81e6e8..a24b38c 100644
--- a/data/loki.yaml
+++ b/data/loki.yaml
@@ -25,7 +25,7 @@ parameters:
     description: Expose Grafana Loki on `localhost:3100`.
   - type: -v
     value: /local/path/to/config:/etc/loki/local-config.yaml
-    description: Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04).
+    description: Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04).
   - type: -v
     value: lokidata:/loki
     description: Persist data in a docker volume named `lokidata`.
@@ -37,7 +37,7 @@ microk8s:
     files:
       - key: promtail
         name: promtail-local-config-k8s.yaml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04
     access: You will now be able to connect to the Loki instance on `http://localhost:31000`.
diff --git a/data/memcached.yaml b/data/memcached.yaml
index 257d74d..f0d4542 100644
--- a/data/memcached.yaml
+++ b/data/memcached.yaml
@@ -16,6 +16,11 @@ releases:
     risk: beta
     version: '1.6.9'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '1.6'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -101,5 +106,5 @@ debug:
     In this case you can append the flags themselves or a shell script to the run command.
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04
     access: Memcached will be listening on port `31211` in your host.
diff --git a/data/mysql.yaml b/data/mysql.yaml
index ad75ce0..4e9304e 100644
--- a/data/mysql.yaml
+++ b/data/mysql.yaml
@@ -19,6 +19,11 @@ releases:
     risk: beta
     version: '8.0.27'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '8.0'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -89,7 +94,7 @@ parameters:
     description: Persist data instead of initializing a new database every time you launch a new container.
   - type: -v
     value: /path/to/config/files/:/etc/mysql/mysql.conf.d/
-    description: Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)).
+    description: Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)).
 debug:
   extraparagraph: |
     #### Initialization Scripts
@@ -110,7 +115,7 @@ microk8s:
     files:
       - key: main-config
         name: my-custom.cnf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04
     access: You will now be able to connect to the MySQL server on `localhost:30306`.
diff --git a/data/nginx.yaml b/data/nginx.yaml
index 73febd5..89e96f0 100644
--- a/data/nginx.yaml
+++ b/data/nginx.yaml
@@ -16,6 +16,11 @@ releases:
     risk: beta
     version: '1.18.0'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '1.18'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -64,7 +69,7 @@ parameters:
     description: Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`).
   - type: -v
     value: /path/to/nginx.conf:/etc/nginx/nginx.conf
-    description: Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)).
+    description: Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)).
 debug:
   - nothing
 microk8s:
@@ -72,10 +77,10 @@ microk8s:
     files:
       - key: nginx
         name: nginx.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04
       - key: nginx-site
         name: index.html
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04
     access: You will now be able to connect to the nginx server on `http://localhost:31080`.
diff --git a/data/postgres.yaml b/data/postgres.yaml
index 375decc..a6227e2 100644
--- a/data/postgres.yaml
+++ b/data/postgres.yaml
@@ -16,6 +16,11 @@ releases:
     risk: beta
     version: '13.1'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '14'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -80,7 +85,7 @@ parameters:
     description: Expose Postgres on `localhost:30432`.
   - type: -v
     value: /path/to/postgresql.conf:/etc/postgresql/postgresql.conf
-    description: Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)).
+    description: Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)).
   - type: -v
     value: /path/to/persisted/data:/var/lib/postgresql/data
     description: Persist data instead of initializing a new database every time you launch a new container.
@@ -104,7 +109,7 @@ microk8s:
     files:
       - key: main-config
         name: postgresql.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04
     access: You will now be able to connect to the Postgres server on `localhost:30306`.
diff --git a/data/prometheus-alertmanager.yaml b/data/prometheus-alertmanager.yaml
index 234416d..8c01e04 100644
--- a/data/prometheus-alertmanager.yaml
+++ b/data/prometheus-alertmanager.yaml
@@ -66,7 +66,7 @@ parameters:
     description: Expose Prometheus Alertmanager on `localhost:30093`.
   - type: -v
     value: /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml
-    description: Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)).
+    description: Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)).
   - type: -v
     value: /path/to/persisted/data:/alertmanager
     description: "Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container."
@@ -78,7 +78,7 @@ microk8s:
     files:
       - key: alertmanager
         name: alertmanager.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04
     access: You will now be able to connect to the Prometheus Alertmanager server on `localhost:30093`.
diff --git a/data/prometheus.yaml b/data/prometheus.yaml
index 2ce4e1e..bb5ab1d 100644
--- a/data/prometheus.yaml
+++ b/data/prometheus.yaml
@@ -80,10 +80,10 @@ parameters:
     description: Expose Prometheus server on `localhost:30090`.
   - type: -v
     value: /path/to/prometheus.yml:/etc/prometheus/prometheus.yml
-    description: Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)).
+    description: Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)).
   - type: -v
     value: /path/to/alerts.yml:/etc/prometheus/alerts.yml
-    description: Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)).
+    description: Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)).
 debug:
   - nothing
 microk8s:
@@ -91,10 +91,10 @@ microk8s:
     files:
       - key: prometheus
         name: prometheus.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04
       - key: prometheus-alerts
         name: alerts.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04
     access: You will now be able to connect to the Prometheus on `http://localhost:30090`.
diff --git a/data/redis.yaml b/data/redis.yaml
index 7b6089c..bbf6465 100644
--- a/data/redis.yaml
+++ b/data/redis.yaml
@@ -18,6 +18,11 @@ releases:
     base: '21.10'
     version: '6.0.15'
     risk: beta
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '6.2'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -81,7 +86,7 @@ parameters:
   - type: -v
     value: /path/to/redis.conf:/etc/redis/redis.conf
     description: >
-      Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)).
+      Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)).
       **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
 debug:
   network:
@@ -102,7 +107,7 @@ microk8s:
     files:
       - key: redis
         name: redis.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04
     access: You will now be able to connect to the Redis server on `localhost:30073`.
diff --git a/data/squid.yaml b/data/squid.yaml
index e5c20f6..7a338e8 100644
--- a/data/squid.yaml
+++ b/data/squid.yaml
@@ -20,6 +20,11 @@ releases:
     risk: beta
     version: '4.13'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '5.2'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -66,7 +71,7 @@ microk8s:
     files:
       - key: squid
         name: squid.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04
     access: You can now access the squid proxy on port 3128
diff --git a/data/telegraf.yaml b/data/telegraf.yaml
index aacae43..ab3262b 100644
--- a/data/telegraf.yaml
+++ b/data/telegraf.yaml
@@ -15,6 +15,11 @@ releases:
     risk: beta
     version: '1.19.2'
     base: '21.10'
+    deprecated:
+      date: '07/2022'
+      path:
+        track: '1.21'
+        base: '22.04'
     architectures:
       - amd64
       - arm64
@@ -61,7 +66,7 @@ parameters:
     description: Expose Telegraf on `localhost:30273`.
   - type: -v
     value: /path/to/telegraf.conf:/etc/telegraf/telegraf.conf
-    description: Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)).
+    description: Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)).
 debug:
     - nothing
 microk8s:
@@ -69,7 +74,7 @@ microk8s:
     files:
       - key: main-config
         name: telegraf.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04
+        link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04
     access: You will now be able to connect to the Telegraf server on `localhost:30073`.
diff --git a/data/zookeeper.yaml b/data/zookeeper.yaml
index 213225a..eb5beef 100644
--- a/data/zookeeper.yaml
+++ b/data/zookeeper.yaml
@@ -32,5 +32,5 @@ debug:
   - nothing
 microk8s:
   deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04
+    link: https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04
     access: Apache Kafka will be available on the K8s cluster as a `kafka-service` Service.
diff --git a/docs/docker.io/ubuntu/apache2.md b/docs/docker.io/ubuntu/apache2.md
index b77a473..54a9389 100644
--- a/docs/docker.io/ubuntu/apache2.md
+++ b/docs/docker.io/ubuntu/apache2.md
@@ -1,6 +1,9 @@
 # Apache2 | Ubuntu
 
-Current Apache2 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache2 or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Apache2 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache2 and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Apache2
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/apache2 but are shown here for comp
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`2.4-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Apache2 2.4 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `2.4-21.10_beta` &nbsp;&nbsp; |  | | Apache2 2.4.48 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `2.4-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Apache2 2.4.41 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,7 +52,7 @@ Access your Apache2 server at `http://localhost:8080`.
 | `-e TZ=UTC` | Timezone. |
 | `-p 8080:80` | Expose Apache2 on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
-| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
+| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
 
 
 #### Testing/Debugging
@@ -68,8 +75,8 @@ docker exec -it apache2-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[apache2.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
-[apache2-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `ubuntu/apache2:2.4-22.04_beta`), then:
+[apache2.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
+[apache2-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `ubuntu/apache2:2.4-22.04_beta`), then:
 
 ```sh
 kubectl create configmap apache2-config --from-file=apache2=apache2.conf --from-file=apache2-site=index.html
@@ -96,6 +103,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~2.4-21.04~~ | Apache2 2.4.46 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 2.4-21.10_beta |
+ | ~~2.4-21.10~~ | Apache2 2.4.48 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 2.4-22.04_beta |
+ | ~~2.4-21.04~~ | Apache2 2.4.46 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~2.4-21.10~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/bind9.md b/docs/docker.io/ubuntu/bind9.md
index 327f7c7..724f510 100644
--- a/docs/docker.io/ubuntu/bind9.md
+++ b/docs/docker.io/ubuntu/bind9.md
@@ -1,6 +1,9 @@
 # Bind9 | Ubuntu
 
-Current Bind9 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Bind9 or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Bind9 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Bind9 and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Bind9
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/bind9 but are shown here for comple
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`9.18-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Bind9 9.18 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `9.16-21.10_beta` &nbsp;&nbsp; |  | | Bind9 9.16.15 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `9.16-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Bind9 9.16.1 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,7 +52,7 @@ Access your Bind9 server at `localhost:30053`
 | `-e TZ=UTC` | Timezone. |
 | `-p 30053:53` | Expose bind9 on `localhost:30053`. |
 | `-e BIND9_USER=bind` | The user which will start the `named` process. |
-| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
+| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
 | `-v /path/to/cached/data:/var/cache/bind` | Location where locally cached data can be dumped. |
 | `-v /path/to/resource/records:/var/lib/bind` | Location of Resource Records defining various domain information. |
 
@@ -70,7 +77,7 @@ docker exec -it bind9-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[bind9-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `ubuntu/bind9:9.18-22.04_beta`), then:
+[bind9-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `ubuntu/bind9:9.18-22.04_beta`), then:
 
 ```sh
 kubectl apply -f bind9-deployment.yml
@@ -96,5 +103,6 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~9.16-21.10~~ | Bind9 9.16.15 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 9.18-22.04_beta |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/cassandra.md b/docs/docker.io/ubuntu/cassandra.md
index eb04d92..a335b1b 100644
--- a/docs/docker.io/ubuntu/cassandra.md
+++ b/docs/docker.io/ubuntu/cassandra.md
@@ -1,6 +1,9 @@
 # Apache Cassandra | Ubuntu
 
-Current Apache Cassandra Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache Cassandra or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Apache Cassandra Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache Cassandra and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Apache Cassandra
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/cassandra but are shown here for co
  | **`4.0-22.04_beta`** &nbsp;&nbsp; |  | | Apache Cassandra 4.0 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -70,7 +78,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cassandra:4.0-22.04_beta`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cassandra:4.0-22.04_beta`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/docs/docker.io/ubuntu/cortex.md b/docs/docker.io/ubuntu/cortex.md
index 5e618f0..adb61d6 100644
--- a/docs/docker.io/ubuntu/cortex.md
+++ b/docs/docker.io/ubuntu/cortex.md
@@ -1,6 +1,9 @@
 # Cortex | Ubuntu
 
-Current Cortex Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Cortex or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Cortex Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Cortex and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Cortex
@@ -29,7 +32,12 @@ _Tags in italics are not available in ubuntu/cortex but are shown here for compl
  | **`1.11-22.04_beta`** &nbsp;&nbsp; |  | | Cortex 1.11 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -49,7 +57,7 @@ Access your Cortex server at `http://localhost:32709`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 32709:9009` | Expose Cortex on `localhost:32709`. |
-| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
+| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
 
 
 #### Testing/Debugging
@@ -72,8 +80,8 @@ docker exec -it cortex-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cortex.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
-[cortex-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cortex:1.11-22.04_beta`), then:
+[cortex.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
+[cortex-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cortex:1.11-22.04_beta`), then:
 
 ```sh
 kubectl create configmap cortex-config --from-file=main-config=cortex.yaml
diff --git a/docs/docker.io/ubuntu/grafana.md b/docs/docker.io/ubuntu/grafana.md
index e92143e..b202456 100644
--- a/docs/docker.io/ubuntu/grafana.md
+++ b/docs/docker.io/ubuntu/grafana.md
@@ -1,6 +1,9 @@
 # Grafana™ software | Ubuntu
 
-Current Grafana™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Grafana™ software or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Grafana™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Grafana™ software and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Grafana™ software
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/grafana but are shown here for comp
  | **`8.2-22.04_beta`** &nbsp;&nbsp; |  | | Grafana™ software 8.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -66,8 +74,8 @@ docker exec -it grafana-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[datasource.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
-[grafana-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `ubuntu/grafana:8.2-22.04_beta`), then:
+[datasource.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
+[grafana-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `ubuntu/grafana:8.2-22.04_beta`), then:
 
 ```sh
 kubectl create configmap grafana-config --from-file=grafana-datasource=datasource.yml --from-file=grafana-dashboard-definition=dashboard.yml --from-file=grafana-dashboard=system-stats-dashboard.json
diff --git a/docs/docker.io/ubuntu/kafka.md b/docs/docker.io/ubuntu/kafka.md
index 2e6880d..2cec666 100644
--- a/docs/docker.io/ubuntu/kafka.md
+++ b/docs/docker.io/ubuntu/kafka.md
@@ -1,6 +1,9 @@
 # Apache Kafka | Ubuntu
 
-Current Apache Kafka Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache Kafka or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Apache Kafka Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache Kafka and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Apache Kafka
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/kafka but are shown here for comple
  | **`3.1-22.04_beta`** &nbsp;&nbsp; |  | | Apache Kafka 3.1.0 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -70,7 +78,7 @@ docker exec -it kafka-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[kafka-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `ubuntu/kafka:3.1-22.04_beta`), then:
+[kafka-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `ubuntu/kafka:3.1-22.04_beta`), then:
 
 ```sh
 kubectl apply -f kafka-deployment.yml
diff --git a/docs/docker.io/ubuntu/loki.md b/docs/docker.io/ubuntu/loki.md
index bfc31b2..b07ed80 100644
--- a/docs/docker.io/ubuntu/loki.md
+++ b/docs/docker.io/ubuntu/loki.md
@@ -1,6 +1,9 @@
 # Grafana Loki™ software | Ubuntu
 
-Current Grafana Loki™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Grafana Loki™ software or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Grafana Loki™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Grafana Loki™ software and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Grafana Loki™ software
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/loki but are shown here for complet
  | **`2.4-22.04_beta`** &nbsp;&nbsp; |  | | Grafana Loki™ software 2.4.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -42,7 +50,7 @@ You can now use your Loki instance exposed at `http://localhost:3100`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 3100:3100` | Expose Grafana Loki on `localhost:3100`. |
-| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
+| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
 | `-v lokidata:/loki` | Persist data in a docker volume named `lokidata`. |
 
 
@@ -66,8 +74,8 @@ docker exec -it loki-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[promtail-local-config-k8s.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
-[loki-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `ubuntu/loki:2.4-22.04_beta`), then:
+[promtail-local-config-k8s.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
+[loki-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `ubuntu/loki:2.4-22.04_beta`), then:
 
 ```sh
 kubectl create configmap promtail-config --from-file=promtail=promtail-local-config-k8s.yaml
diff --git a/docs/docker.io/ubuntu/memcached.md b/docs/docker.io/ubuntu/memcached.md
index 29d33e1..3e170b9 100644
--- a/docs/docker.io/ubuntu/memcached.md
+++ b/docs/docker.io/ubuntu/memcached.md
@@ -1,6 +1,9 @@
 # Memcached | Ubuntu
 
-Current Memcached Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Memcached or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Memcached Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Memcached and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Memcached
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/memcached but are shown here for co
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`1.6-22.04_beta`** &nbsp;&nbsp; |  | | Memcached 1.6 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.6-21.10_beta` &nbsp;&nbsp; |  | | Memcached 1.6.9 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `1.5-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Memcached 1.5.22 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -99,7 +106,7 @@ In this case you can append the flags themselves or a shell script to the run co
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[memcached-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `ubuntu/memcached:1.6-22.04_beta`), then:
+[memcached-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `ubuntu/memcached:1.6-22.04_beta`), then:
 
 ```sh
 kubectl apply -f memcached-deployment.yml
@@ -125,6 +132,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.6-21.04~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.6-21.10_beta |
+ | ~~1.6-21.10~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.6-22.04_beta |
+ | ~~1.6-21.04~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.6-21.10~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/mysql.md b/docs/docker.io/ubuntu/mysql.md
index e1b2916..8f17bfa 100644
--- a/docs/docker.io/ubuntu/mysql.md
+++ b/docs/docker.io/ubuntu/mysql.md
@@ -1,6 +1,9 @@
 # MySQL™ software | Ubuntu
 
-Current MySQL™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer MySQL™ software or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current MySQL™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of MySQL™ software and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About MySQL™ software
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/mysql but are shown here for comple
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`8.0-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | MySQL™ software 8.0 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `8.0-21.10_beta` &nbsp;&nbsp; |  | | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `8.0-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | MySQL™ software 8.0.22 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -53,7 +60,7 @@ Access your MySQL server at `localhost:30306`.
 | `-e MYSQL_INITSB_SKIP_TZINFO=yes` | Timezone data is automatically loaded via entrypoint script, set this variable to any non-empty value to disable it. |
 | `-p 30306:3306` | Expose MySQL server on `localhost:30306`. |
 | `-v /path/to/data:/var/lib/mysql` | Persist data instead of initializing a new database every time you launch a new container. |
-| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
+| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
 
 #### Initialization Scripts
 
@@ -94,8 +101,8 @@ The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[my-custom.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
-[mysql-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `ubuntu/mysql:8.0-22.04_beta`), then:
+[my-custom.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
+[mysql-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `ubuntu/mysql:8.0-22.04_beta`), then:
 
 ```sh
 kubectl create configmap mysql-config --from-file=main-config=my-custom.cnf
@@ -122,6 +129,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~8.0-21.04~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 8.0-21.10_beta |
+ | ~~8.0-21.10~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 8.0-22.04_beta |
+ | ~~8.0-21.04~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~8.0-21.10~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/nginx.md b/docs/docker.io/ubuntu/nginx.md
index e83354c..955f720 100644
--- a/docs/docker.io/ubuntu/nginx.md
+++ b/docs/docker.io/ubuntu/nginx.md
@@ -1,6 +1,9 @@
 # Nginx | Ubuntu
 
-Current Nginx Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Nginx or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Nginx Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Nginx and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Nginx
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/nginx but are shown here for comple
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`1.18-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Nginx 1.18 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.18-21.10_beta` &nbsp;&nbsp; |  | | Nginx 1.18.0 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `1.18-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Nginx 1.18.0 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -46,7 +53,7 @@ Access your Nginx server at `http://localhost:8080`.
 | `-p 8080:80` | Expose Nginx on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
 | `-v /path/to/conf.template:/etc/nginx/templates/conf.template` | Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`). |
-| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
+| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
 
 
 #### Testing/Debugging
@@ -69,8 +76,8 @@ docker exec -it nginx-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[nginx.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
-[nginx-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `ubuntu/nginx:1.18-22.04_beta`), then:
+[nginx.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
+[nginx-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `ubuntu/nginx:1.18-22.04_beta`), then:
 
 ```sh
 kubectl create configmap nginx-config --from-file=nginx=nginx.conf --from-file=nginx-site=index.html
@@ -97,6 +104,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.18-21.04~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.18-21.10_beta |
+ | ~~1.18-21.10~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.18-22.04_beta |
+ | ~~1.18-21.04~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.18-21.10~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/postgres.md b/docs/docker.io/ubuntu/postgres.md
index 7cb092c..9f95cf0 100644
--- a/docs/docker.io/ubuntu/postgres.md
+++ b/docs/docker.io/ubuntu/postgres.md
@@ -1,6 +1,9 @@
 # Postgres | Ubuntu
 
-Current Postgres Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Postgres or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Postgres Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Postgres and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Postgres
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/postgres but are shown here for com
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`14-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Postgres 14 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `13-21.10_beta` &nbsp;&nbsp; |  | | Postgres 13.1 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `12-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Postgres 12.4 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -51,7 +58,7 @@ Access your PostgreSQL server at `localhost:30432`.
 | `-e POSTGRES_HOST_AUTH_METHOD=trust` | Set the `auth-method` for `host` connections for `all` databases, `all` users, and `all` addresses. The following will be added to the `pg_hba.conf` if this option is passed: `host all all all $POSTGRES_HOST_AUTH_METHOD`. |
 | `-e PGDATA=/path/to/location` | Set the location of the database files. The default is `/var/lib/postgresql/data`. |
 | `-p 30432:5432` | Expose Postgres on `localhost:30432`. |
-| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
+| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
 | `-v /path/to/persisted/data:/var/lib/postgresql/data` | Persist data instead of initializing a new database every time you launch a new container. |
 
 #### Initialization Scripts
@@ -93,8 +100,8 @@ The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[postgresql.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
-[postgres-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `ubuntu/postgres:14-22.04_beta`), then:
+[postgresql.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
+[postgres-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `ubuntu/postgres:14-22.04_beta`), then:
 
 ```sh
 kubectl create configmap postgres-config --from-file=main-config=postgresql.conf
@@ -121,6 +128,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~13-21.10~~ | Postgres 13.1 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 14-22.04_beta |
  | ~~13-21.04~~ | Postgres 13.1 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~13.1-21.10~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/prometheus-alertmanager.md b/docs/docker.io/ubuntu/prometheus-alertmanager.md
index a06fffe..6f8562a 100644
--- a/docs/docker.io/ubuntu/prometheus-alertmanager.md
+++ b/docs/docker.io/ubuntu/prometheus-alertmanager.md
@@ -1,6 +1,9 @@
 # Prometheus Alertmanager | Ubuntu
 
-Current Prometheus Alertmanager Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Prometheus Alertmanager or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Prometheus Alertmanager Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Prometheus Alertmanager and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Prometheus Alertmanager
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/prometheus-alertmanager but are sho
  | **`0.23-22.04_beta`** &nbsp;&nbsp; |  | | Prometheus Alertmanager 0.23 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -42,7 +50,7 @@ Access your Prometheus Alertmanager server at `localhost:30093`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30093:9093` | Expose Prometheus Alertmanager on `localhost:30093`. |
-| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
+| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
 | `-v /path/to/persisted/data:/alertmanager` | Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container. |
 
 
@@ -66,8 +74,8 @@ docker exec -it prometheus-alertmanager-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[alertmanager.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
-[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `ubuntu/prometheus-alertmanager:0.23-22.04_beta`), then:
+[alertmanager.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
+[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `ubuntu/prometheus-alertmanager:0.23-22.04_beta`), then:
 
 ```sh
 kubectl create configmap alertmanager-config --from-file=alertmanager=alertmanager.yml
diff --git a/docs/docker.io/ubuntu/prometheus.md b/docs/docker.io/ubuntu/prometheus.md
index 52e94f1..ea2d8c6 100644
--- a/docs/docker.io/ubuntu/prometheus.md
+++ b/docs/docker.io/ubuntu/prometheus.md
@@ -1,6 +1,9 @@
 # Prometheus | Ubuntu
 
-Current Prometheus Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Prometheus or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Prometheus Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Prometheus and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Prometheus
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/prometheus but are shown here for c
  | **`2.33-22.04_beta`** &nbsp;&nbsp; |  | | Prometheus 2.33 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -42,8 +50,8 @@ Access your Prometheus server at `localhost:30090`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30090:9090` | Expose Prometheus server on `localhost:30090`. |
-| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
-| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
+| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
+| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
 
 
 #### Testing/Debugging
@@ -66,8 +74,8 @@ docker exec -it prometheus-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[prometheus.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
-[prometheus-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `ubuntu/prometheus:2.33-22.04_beta`), then:
+[prometheus.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
+[prometheus-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `ubuntu/prometheus:2.33-22.04_beta`), then:
 
 ```sh
 kubectl create configmap prometheus-config --from-file=prometheus=prometheus.yml --from-file=prometheus-alerts=alerts.yml
diff --git a/docs/docker.io/ubuntu/redis.md b/docs/docker.io/ubuntu/redis.md
index 34330ab..112c4ce 100644
--- a/docs/docker.io/ubuntu/redis.md
+++ b/docs/docker.io/ubuntu/redis.md
@@ -1,6 +1,9 @@
 # Redis™ software | Ubuntu
 
-Current Redis™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Redis™ software or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Redis™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Redis™ software and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Redis™ software
@@ -20,10 +23,14 @@ _Tags in italics are not available in ubuntu/redis but are shown here for comple
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`6.2-22.04_beta`** &nbsp;&nbsp; |  | | Redis™ software 6.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `6.0-21.10_beta` &nbsp;&nbsp; |  | | Redis™ software 6.0.15 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -48,7 +55,7 @@ Access your Redis server at `localhost:30073`.
 | `-e REDIS_ALLOW_REMOTE_CONNECTIONS=yes` | Set to `no` to disallow remote connections to `redis-server` (i.e., make `redis-server` listen to `127.0.0.1` only). |
 | `-e REDIS_EXTRA_FLAGS` | Specify extra flags to be passed to `redis-server` when initializing it. |
 | `-p 30073:6379` | Expose redis on `localhost:30073`. |
-| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
+| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
  |
 
 
@@ -88,8 +95,8 @@ redis:6379>
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[redis.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
-[redis-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `ubuntu/redis:6.2-22.04_beta`), then:
+[redis.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
+[redis-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `ubuntu/redis:6.2-22.04_beta`), then:
 
 ```sh
 kubectl create configmap redis-config --from-file=redis=redis.conf
@@ -116,7 +123,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~6.0-21.04~~ | Redis™ software 6.0.11 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 6.0-21.10_beta |
+ | ~~6.0-21.10~~ | Redis™ software 6.0.15 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 6.2-22.04_beta |
+ | ~~6.0-21.04~~ | Redis™ software 6.0.11 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~6.0-21.10~~ |
  | ~~5.0-20.04~~ | Redis™ software 5.0.7 on Ubuntu&nbsp;20.04&nbsp;LTS | 01/2021 | ~~6.0-21.04~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/squid.md b/docs/docker.io/ubuntu/squid.md
index 15c055f..8023c71 100644
--- a/docs/docker.io/ubuntu/squid.md
+++ b/docs/docker.io/ubuntu/squid.md
@@ -1,6 +1,9 @@
 # Squid | Ubuntu
 
-Current Squid Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Squid or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Squid Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Squid and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Squid
@@ -20,11 +23,15 @@ _Tags in italics are not available in ubuntu/squid but are shown here for comple
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`5.2-22.04_beta`** &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Squid 5.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `4.13-21.10_beta` &nbsp;&nbsp; |  | | Squid 4.13 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
  | `4.10-20.04_beta` &nbsp;&nbsp; | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) | | Squid 4.10 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -70,8 +77,8 @@ docker exec -it squid-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[squid.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
-[squid-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `ubuntu/squid:5.2-22.04_beta`), then:
+[squid.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
+[squid-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `ubuntu/squid:5.2-22.04_beta`), then:
 
 ```sh
 kubectl create configmap squid-config --from-file=squid=squid.conf
@@ -98,5 +105,6 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~4.13-21.10~~ | Squid 4.13 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 5.2-22.04_beta |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/telegraf.md b/docs/docker.io/ubuntu/telegraf.md
index cfb8f51..cae8c16 100644
--- a/docs/docker.io/ubuntu/telegraf.md
+++ b/docs/docker.io/ubuntu/telegraf.md
@@ -1,6 +1,9 @@
 # Telegraf™ software | Ubuntu
 
-Current Telegraf™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Telegraf™ software or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Telegraf™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Telegraf™ software and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Telegraf™ software
@@ -20,10 +23,14 @@ _Tags in italics are not available in ubuntu/telegraf but are shown here for com
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`1.21-22.04_beta`** &nbsp;&nbsp; |  | | Telegraf™ software 1.21 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.19-21.10_beta` &nbsp;&nbsp; |  | | Telegraf™ software 1.19.2 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -43,7 +50,7 @@ Access your Telegraf server at `localhost:30273`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30273:9273` | Expose Telegraf on `localhost:30273`. |
-| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
+| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
 
 
 #### Testing/Debugging
@@ -66,8 +73,8 @@ docker exec -it telegraf-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[telegraf.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
-[telegraf-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `ubuntu/telegraf:1.21-22.04_beta`), then:
+[telegraf.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
+[telegraf-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `ubuntu/telegraf:1.21-22.04_beta`), then:
 
 ```sh
 kubectl create configmap telegraf-config --from-file=main-config=telegraf.conf
@@ -94,7 +101,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.17-21.04~~ | Telegraf™ software 1.17.2 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.19-21.10_beta |
+ | ~~1.19-21.10~~ | Telegraf™ software 1.19.2 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.21-22.04_beta |
+ | ~~1.17-21.04~~ | Telegraf™ software 1.17.2 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.19-21.10~~ |
  | ~~1.15-20.04~~ | Telegraf™ software 1.15.2 on Ubuntu&nbsp;20.04&nbsp;LTS | 01/2021 | ~~1.17-21.04~~ |
 | _`track`_ |
 
diff --git a/docs/docker.io/ubuntu/zookeeper.md b/docs/docker.io/ubuntu/zookeeper.md
index 98180d0..abcf9ed 100644
--- a/docs/docker.io/ubuntu/zookeeper.md
+++ b/docs/docker.io/ubuntu/zookeeper.md
@@ -1,6 +1,9 @@
 # Apache ZooKeeper | Ubuntu
 
-Current Apache ZooKeeper Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache ZooKeeper or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current Apache ZooKeeper Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache ZooKeeper and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 
 
 ## About Apache ZooKeeper
@@ -22,7 +25,12 @@ _Tags in italics are not available in ubuntu/zookeeper but are shown here for co
  | **`3.1-22.04_beta`** &nbsp;&nbsp; |  | | Apache ZooKeeper 3.1.0 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes commercial redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -65,7 +73,7 @@ docker exec -it zookeeper-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[zookeeper-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `ubuntu/zookeeper:3.1-22.04_beta`), then:
+[zookeeper-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `ubuntu/zookeeper:3.1-22.04_beta`), then:
 
 ```sh
 kubectl apply -f zookeeper-deployment.yml
diff --git a/docs/public.ecr.aws/lts/apache2.md b/docs/public.ecr.aws/lts/apache2.md
index 93dc477..31e002a 100644
--- a/docs/public.ecr.aws/lts/apache2.md
+++ b/docs/public.ecr.aws/lts/apache2.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/apache2`. [Request 
  | `2.4-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | Apache2 2.4.41 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -48,7 +53,7 @@ Access your Apache2 server at `http://localhost:8080`.
 | `-e TZ=UTC` | Timezone. |
 | `-p 8080:80` | Expose Apache2 on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
-| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
+| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
 
 
 #### Testing/Debugging
@@ -71,8 +76,8 @@ docker exec -it apache2-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[apache2.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
-[apache2-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/apache2:2.4-22.04_beta`), then:
+[apache2.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
+[apache2-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/apache2:2.4-22.04_beta`), then:
 
 ```sh
 kubectl create configmap apache2-config --from-file=apache2=apache2.conf --from-file=apache2-site=index.html
diff --git a/docs/public.ecr.aws/lts/bind9.md b/docs/public.ecr.aws/lts/bind9.md
index f30b9e1..1ddc90e 100644
--- a/docs/public.ecr.aws/lts/bind9.md
+++ b/docs/public.ecr.aws/lts/bind9.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/bind9`. [Request ac
  | `9.16-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | Bind9 9.16.1 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -48,7 +53,7 @@ Access your Bind9 server at `localhost:30053`
 | `-e TZ=UTC` | Timezone. |
 | `-p 30053:53` | Expose bind9 on `localhost:30053`. |
 | `-e BIND9_USER=bind` | The user which will start the `named` process. |
-| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
+| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
 | `-v /path/to/cached/data:/var/cache/bind` | Location where locally cached data can be dumped. |
 | `-v /path/to/resource/records:/var/lib/bind` | Location of Resource Records defining various domain information. |
 
@@ -73,7 +78,7 @@ docker exec -it bind9-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[bind9-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/bind9:9.18-22.04_beta`), then:
+[bind9-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/bind9:9.18-22.04_beta`), then:
 
 ```sh
 kubectl apply -f bind9-deployment.yml
diff --git a/docs/public.ecr.aws/lts/cassandra.md b/docs/public.ecr.aws/lts/cassandra.md
index f342728..233b1d1 100644
--- a/docs/public.ecr.aws/lts/cassandra.md
+++ b/docs/public.ecr.aws/lts/cassandra.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/cassandra`. [Reques
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -73,7 +78,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cassandra:latest`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cassandra:latest`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/docs/public.ecr.aws/lts/cortex.md b/docs/public.ecr.aws/lts/cortex.md
index 22ff38a..80e8469 100644
--- a/docs/public.ecr.aws/lts/cortex.md
+++ b/docs/public.ecr.aws/lts/cortex.md
@@ -29,7 +29,12 @@ Up to 10 years customer security maintenance `from canonical/cortex`. [Request a
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -52,7 +57,7 @@ Access your Cortex server at `http://localhost:32709`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 32709:9009` | Expose Cortex on `localhost:32709`. |
-| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
+| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
 
 
 #### Testing/Debugging
@@ -75,8 +80,8 @@ docker exec -it cortex-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cortex.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
-[cortex-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cortex:latest`), then:
+[cortex.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
+[cortex-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cortex:latest`), then:
 
 ```sh
 kubectl create configmap cortex-config --from-file=main-config=cortex.yaml
diff --git a/docs/public.ecr.aws/lts/grafana.md b/docs/public.ecr.aws/lts/grafana.md
index eee018e..4c9656a 100644
--- a/docs/public.ecr.aws/lts/grafana.md
+++ b/docs/public.ecr.aws/lts/grafana.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/grafana`. [Request 
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -69,8 +74,8 @@ docker exec -it grafana-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[datasource.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
-[grafana-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/grafana:latest`), then:
+[datasource.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
+[grafana-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/grafana:latest`), then:
 
 ```sh
 kubectl create configmap grafana-config --from-file=grafana-datasource=datasource.yml --from-file=grafana-dashboard-definition=dashboard.yml --from-file=grafana-dashboard=system-stats-dashboard.json
diff --git a/docs/public.ecr.aws/lts/kafka.md b/docs/public.ecr.aws/lts/kafka.md
index b5a607c..c4b0144 100644
--- a/docs/public.ecr.aws/lts/kafka.md
+++ b/docs/public.ecr.aws/lts/kafka.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/kafka`. [Request ac
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -73,7 +78,7 @@ docker exec -it kafka-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[kafka-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/kafka:latest`), then:
+[kafka-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/kafka:latest`), then:
 
 ```sh
 kubectl apply -f kafka-deployment.yml
diff --git a/docs/public.ecr.aws/lts/loki.md b/docs/public.ecr.aws/lts/loki.md
index ecf492d..b20e29d 100644
--- a/docs/public.ecr.aws/lts/loki.md
+++ b/docs/public.ecr.aws/lts/loki.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/loki`. [Request acc
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,7 +50,7 @@ You can now use your Loki instance exposed at `http://localhost:3100`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 3100:3100` | Expose Grafana Loki on `localhost:3100`. |
-| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
+| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
 | `-v lokidata:/loki` | Persist data in a docker volume named `lokidata`. |
 
 
@@ -69,8 +74,8 @@ docker exec -it loki-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[promtail-local-config-k8s.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
-[loki-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/loki:latest`), then:
+[promtail-local-config-k8s.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
+[loki-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/loki:latest`), then:
 
 ```sh
 kubectl create configmap promtail-config --from-file=promtail=promtail-local-config-k8s.yaml
diff --git a/docs/public.ecr.aws/lts/memcached.md b/docs/public.ecr.aws/lts/memcached.md
index f1682e8..8bd56f1 100644
--- a/docs/public.ecr.aws/lts/memcached.md
+++ b/docs/public.ecr.aws/lts/memcached.md
@@ -23,7 +23,12 @@ Up to 10 years customer security maintenance `from canonical/memcached`. [Reques
  | **`1.5-20.04_beta`** &nbsp;&nbsp; | 04/2025 | 04/2030 | Memcached 1.5.22 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -101,7 +106,7 @@ In this case you can append the flags themselves or a shell script to the run co
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[memcached-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/memcached:1.5-20.04_beta`), then:
+[memcached-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/memcached:1.5-20.04_beta`), then:
 
 ```sh
 kubectl apply -f memcached-deployment.yml
diff --git a/docs/public.ecr.aws/lts/mysql.md b/docs/public.ecr.aws/lts/mysql.md
index 86d8d62..b9360f1 100644
--- a/docs/public.ecr.aws/lts/mysql.md
+++ b/docs/public.ecr.aws/lts/mysql.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/mysql`. [Request ac
  | `8.0-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | MySQL™ software 8.0.22 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -56,7 +61,7 @@ Access your MySQL server at `localhost:30306`.
 | `-e MYSQL_INITSB_SKIP_TZINFO=yes` | Timezone data is automatically loaded via entrypoint script, set this variable to any non-empty value to disable it. |
 | `-p 30306:3306` | Expose MySQL server on `localhost:30306`. |
 | `-v /path/to/data:/var/lib/mysql` | Persist data instead of initializing a new database every time you launch a new container. |
-| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
+| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
 
 #### Initialization Scripts
 
@@ -97,8 +102,8 @@ The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[my-custom.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
-[mysql-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/mysql:8.0-22.04_beta`), then:
+[my-custom.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
+[mysql-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/mysql:8.0-22.04_beta`), then:
 
 ```sh
 kubectl create configmap mysql-config --from-file=main-config=my-custom.cnf
diff --git a/docs/public.ecr.aws/lts/nginx.md b/docs/public.ecr.aws/lts/nginx.md
index d9a2b7e..723259b 100644
--- a/docs/public.ecr.aws/lts/nginx.md
+++ b/docs/public.ecr.aws/lts/nginx.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/nginx`. [Request ac
  | `1.18-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | Nginx 1.18.0 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -49,7 +54,7 @@ Access your Nginx server at `http://localhost:8080`.
 | `-p 8080:80` | Expose Nginx on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
 | `-v /path/to/conf.template:/etc/nginx/templates/conf.template` | Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`). |
-| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
+| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
 
 
 #### Testing/Debugging
@@ -72,8 +77,8 @@ docker exec -it nginx-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[nginx.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
-[nginx-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/nginx:1.18-22.04_beta`), then:
+[nginx.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
+[nginx-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/nginx:1.18-22.04_beta`), then:
 
 ```sh
 kubectl create configmap nginx-config --from-file=nginx=nginx.conf --from-file=nginx-site=index.html
diff --git a/docs/public.ecr.aws/lts/postgres.md b/docs/public.ecr.aws/lts/postgres.md
index fe2a004..3f6383b 100644
--- a/docs/public.ecr.aws/lts/postgres.md
+++ b/docs/public.ecr.aws/lts/postgres.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/postgres`. [Request
  | `12-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | Postgres 12.4 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -54,7 +59,7 @@ Access your PostgreSQL server at `localhost:30432`.
 | `-e POSTGRES_HOST_AUTH_METHOD=trust` | Set the `auth-method` for `host` connections for `all` databases, `all` users, and `all` addresses. The following will be added to the `pg_hba.conf` if this option is passed: `host all all all $POSTGRES_HOST_AUTH_METHOD`. |
 | `-e PGDATA=/path/to/location` | Set the location of the database files. The default is `/var/lib/postgresql/data`. |
 | `-p 30432:5432` | Expose Postgres on `localhost:30432`. |
-| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
+| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
 | `-v /path/to/persisted/data:/var/lib/postgresql/data` | Persist data instead of initializing a new database every time you launch a new container. |
 
 #### Initialization Scripts
@@ -96,8 +101,8 @@ The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[postgresql.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
-[postgres-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/postgres:14-22.04_beta`), then:
+[postgresql.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
+[postgres-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/postgres:14-22.04_beta`), then:
 
 ```sh
 kubectl create configmap postgres-config --from-file=main-config=postgresql.conf
diff --git a/docs/public.ecr.aws/lts/prometheus-alertmanager.md b/docs/public.ecr.aws/lts/prometheus-alertmanager.md
index abaebf4..807cdec 100644
--- a/docs/public.ecr.aws/lts/prometheus-alertmanager.md
+++ b/docs/public.ecr.aws/lts/prometheus-alertmanager.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/prometheus-alertman
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,7 +50,7 @@ Access your Prometheus Alertmanager server at `localhost:30093`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30093:9093` | Expose Prometheus Alertmanager on `localhost:30093`. |
-| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
+| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
 | `-v /path/to/persisted/data:/alertmanager` | Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container. |
 
 
@@ -69,8 +74,8 @@ docker exec -it prometheus-alertmanager-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[alertmanager.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
-[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/prometheus-alertmanager:latest`), then:
+[alertmanager.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
+[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/prometheus-alertmanager:latest`), then:
 
 ```sh
 kubectl create configmap alertmanager-config --from-file=alertmanager=alertmanager.yml
diff --git a/docs/public.ecr.aws/lts/prometheus.md b/docs/public.ecr.aws/lts/prometheus.md
index d33d6d3..d3c3543 100644
--- a/docs/public.ecr.aws/lts/prometheus.md
+++ b/docs/public.ecr.aws/lts/prometheus.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/prometheus`. [Reque
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,8 +50,8 @@ Access your Prometheus server at `localhost:30090`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30090:9090` | Expose Prometheus server on `localhost:30090`. |
-| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
-| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
+| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
+| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
 
 
 #### Testing/Debugging
@@ -69,8 +74,8 @@ docker exec -it prometheus-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[prometheus.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
-[prometheus-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/prometheus:latest`), then:
+[prometheus.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
+[prometheus-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/prometheus:latest`), then:
 
 ```sh
 kubectl create configmap prometheus-config --from-file=prometheus=prometheus.yml --from-file=prometheus-alerts=alerts.yml
diff --git a/docs/public.ecr.aws/lts/redis.md b/docs/public.ecr.aws/lts/redis.md
index 67893e5..710da56 100644
--- a/docs/public.ecr.aws/lts/redis.md
+++ b/docs/public.ecr.aws/lts/redis.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/redis`. [Request ac
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -50,7 +55,7 @@ Access your Redis server at `localhost:30073`.
 | `-e REDIS_ALLOW_REMOTE_CONNECTIONS=yes` | Set to `no` to disallow remote connections to `redis-server` (i.e., make `redis-server` listen to `127.0.0.1` only). |
 | `-e REDIS_EXTRA_FLAGS` | Specify extra flags to be passed to `redis-server` when initializing it. |
 | `-p 30073:6379` | Expose redis on `localhost:30073`. |
-| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
+| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
  |
 
 
@@ -90,8 +95,8 @@ redis:6379>
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[redis.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
-[redis-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/redis:latest`), then:
+[redis.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
+[redis-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/redis:latest`), then:
 
 ```sh
 kubectl create configmap redis-config --from-file=redis=redis.conf
diff --git a/docs/public.ecr.aws/lts/squid.md b/docs/public.ecr.aws/lts/squid.md
index 5ab66a1..3ae08b9 100644
--- a/docs/public.ecr.aws/lts/squid.md
+++ b/docs/public.ecr.aws/lts/squid.md
@@ -24,7 +24,12 @@ Up to 10 years customer security maintenance `from canonical/squid`. [Request ac
  | `4.10-20.04_beta` &nbsp;&nbsp; | 04/2025 | 04/2030 | Squid 4.10 on Ubuntu&nbsp;20.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -73,8 +78,8 @@ docker exec -it squid-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[squid.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
-[squid-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/squid:5.2-22.04_beta`), then:
+[squid.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
+[squid-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/squid:5.2-22.04_beta`), then:
 
 ```sh
 kubectl create configmap squid-config --from-file=squid=squid.conf
diff --git a/docs/public.ecr.aws/lts/telegraf.md b/docs/public.ecr.aws/lts/telegraf.md
index a3bb9d5..3ff4ab8 100644
--- a/docs/public.ecr.aws/lts/telegraf.md
+++ b/docs/public.ecr.aws/lts/telegraf.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/telegraf`. [Request
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -45,7 +50,7 @@ Access your Telegraf server at `localhost:30273`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30273:9273` | Expose Telegraf on `localhost:30273`. |
-| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
+| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
 
 
 #### Testing/Debugging
@@ -68,8 +73,8 @@ docker exec -it telegraf-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[telegraf.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
-[telegraf-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/telegraf:latest`), then:
+[telegraf.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
+[telegraf-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/telegraf:latest`), then:
 
 ```sh
 kubectl create configmap telegraf-config --from-file=main-config=telegraf.conf
diff --git a/docs/public.ecr.aws/lts/zookeeper.md b/docs/public.ecr.aws/lts/zookeeper.md
index 9a6c415..b6692b4 100644
--- a/docs/public.ecr.aws/lts/zookeeper.md
+++ b/docs/public.ecr.aws/lts/zookeeper.md
@@ -22,7 +22,12 @@ Up to 10 years customer security maintenance `from canonical/zookeeper`. [Reques
 |---|---|---|---|---|
 | _`track_risk`_ |
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 ### Commercial use and Extended Security Maintenance channels
 If your usage includes redistribution or requires unavailable channels/versions, please [get in touch with the Canonical team](https://ubuntu.com/security/docker-images#get-in-touch) (or using [e-mail]).
@@ -68,7 +73,7 @@ docker exec -it zookeeper-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[zookeeper-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/zookeeper:latest`), then:
+[zookeeper-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/zookeeper:latest`), then:
 
 ```sh
 kubectl apply -f zookeeper-deployment.yml
diff --git a/docs/public.ecr.aws/ubuntu/apache2.md b/docs/public.ecr.aws/ubuntu/apache2.md
index f247eb4..011ec2b 100644
--- a/docs/public.ecr.aws/ubuntu/apache2.md
+++ b/docs/public.ecr.aws/ubuntu/apache2.md
@@ -1,6 +1,7 @@
 # Apache2 | Ubuntu
 
-Current Apache2 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache2 or Ubuntu release.
+Current Apache2 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache2 and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/apache2](https://gallery.ecr.aws/lts/apache2).
 
 ## About Apache2
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/apache2`. [Request 
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`2.4-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/apache2) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/apache2) | Apache2 2.4 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `2.4-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/apache2) | [](https://gallery.ecr.aws/lts/apache2) | Apache2 2.4.48 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/apache2 but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/apache2 but are s
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,7 +46,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~2.4-21.04~~ | Apache2 2.4.46 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 2.4-21.10_beta |
+ | ~~2.4-21.10~~ | Apache2 2.4.48 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 2.4-22.04_beta |
+ | ~~2.4-21.04~~ | Apache2 2.4.46 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~2.4-21.10~~ |
 | _`track`_ |
 
 
@@ -50,7 +56,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name apache2-container -e TZ=UTC -p 8080:80 public.ecr.aws/ubuntu/apache2:2.4-21.04
+docker run -d --name apache2-container -e TZ=UTC -p 8080:80 public.ecr.aws/ubuntu/apache2:2.4-21.10
 ```
 Access your Apache2 server at `http://localhost:8080`.
 
@@ -61,7 +67,7 @@ Access your Apache2 server at `http://localhost:8080`.
 | `-e TZ=UTC` | Timezone. |
 | `-p 8080:80` | Expose Apache2 on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
-| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
+| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04)). |
 
 
 #### Testing/Debugging
@@ -84,8 +90,8 @@ docker exec -it apache2-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[apache2.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
-[apache2-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/apache2:2.4-21.04`), then:
+[apache2.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf?h=2.4-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html?h=2.4-22.04) and
+[apache2-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml?h=2.4-22.04) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/apache2:2.4-21.10`), then:
 
 ```sh
 kubectl create configmap apache2-config --from-file=apache2=apache2.conf --from-file=apache2-site=index.html
diff --git a/docs/public.ecr.aws/ubuntu/bind9.md b/docs/public.ecr.aws/ubuntu/bind9.md
index 3533670..00f6911 100644
--- a/docs/public.ecr.aws/ubuntu/bind9.md
+++ b/docs/public.ecr.aws/ubuntu/bind9.md
@@ -1,6 +1,7 @@
 # Bind9 | Ubuntu
 
-Current Bind9 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Bind9 or Ubuntu release.
+Current Bind9 Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Bind9 and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/bind9](https://gallery.ecr.aws/lts/bind9).
 
 ## About Bind9
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/bind9`. [Request ac
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`9.18-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/bind9) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/bind9) | Bind9 9.18 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `9.16-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/bind9) | [](https://gallery.ecr.aws/lts/bind9) | Bind9 9.16.15 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/bind9 but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/bind9 but are sho
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,6 +46,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~9.16-21.10~~ | Bind9 9.16.15 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 9.18-22.04_beta |
 | _`track`_ |
 
 
@@ -49,7 +55,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name bind9-container -e TZ=UTC -p 30053:53 public.ecr.aws/ubuntu/bind9:9.18-22.04_beta
+docker run -d --name bind9-container -e TZ=UTC -p 30053:53 public.ecr.aws/ubuntu/bind9:9.16-21.10
 ```
 Access your Bind9 server at `localhost:30053`
 
@@ -60,7 +66,7 @@ Access your Bind9 server at `localhost:30053`
 | `-e TZ=UTC` | Timezone. |
 | `-p 30053:53` | Expose bind9 on `localhost:30053`. |
 | `-e BIND9_USER=bind` | The user which will start the `named` process. |
-| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
+| `-v /path/to/bind/configuration:/etc/bind/named.conf` | Local [configuration file](https://bind9.readthedocs.io/en/latest/reference.html) `named.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04)). |
 | `-v /path/to/cached/data:/var/cache/bind` | Location where locally cached data can be dumped. |
 | `-v /path/to/resource/records:/var/lib/bind` | Location of Resource Records defining various domain information. |
 
@@ -85,7 +91,7 @@ docker exec -it bind9-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[bind9-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/bind9:9.18-22.04_beta`), then:
+[bind9-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04) and set `containers.bind9.image` in `bind9-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/bind9:9.16-21.10`), then:
 
 ```sh
 kubectl apply -f bind9-deployment.yml
diff --git a/docs/public.ecr.aws/ubuntu/cassandra.md b/docs/public.ecr.aws/ubuntu/cassandra.md
index 748f0fe..5f3aece 100644
--- a/docs/public.ecr.aws/ubuntu/cassandra.md
+++ b/docs/public.ecr.aws/ubuntu/cassandra.md
@@ -1,6 +1,7 @@
 # Apache Cassandra | Ubuntu
 
-Current Apache Cassandra Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache Cassandra or Ubuntu release.
+Current Apache Cassandra Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache Cassandra and Ubuntu.
 
 ## About Apache Cassandra
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/cassandra`. [Reques
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -80,7 +86,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cassandra:4.0-21.10`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml?h=4.0-22.04) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cassandra:4.0-21.10`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/docs/public.ecr.aws/ubuntu/cortex.md b/docs/public.ecr.aws/ubuntu/cortex.md
index 2fac18a..cbcaa01 100644
--- a/docs/public.ecr.aws/ubuntu/cortex.md
+++ b/docs/public.ecr.aws/ubuntu/cortex.md
@@ -1,6 +1,7 @@
 # Cortex | Ubuntu
 
-Current Cortex Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Cortex or Ubuntu release.
+Current Cortex Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Cortex and Ubuntu.
 
 ## About Cortex
 
@@ -27,7 +28,12 @@ Up to 10 years customer security maintenance `from canonical/cortex`. [Request a
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -59,7 +65,7 @@ Access your Cortex server at `http://localhost:32709`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 32709:9009` | Expose Cortex on `localhost:32709`. |
-| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
+| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04)). |
 
 
 #### Testing/Debugging
@@ -82,8 +88,8 @@ docker exec -it cortex-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cortex.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
-[cortex-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cortex:1.10-21.10`), then:
+[cortex.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml?h=1.11-22.04) and
+[cortex-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml?h=1.11-22.04) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cortex:1.10-21.10`), then:
 
 ```sh
 kubectl create configmap cortex-config --from-file=main-config=cortex.yaml
diff --git a/docs/public.ecr.aws/ubuntu/grafana.md b/docs/public.ecr.aws/ubuntu/grafana.md
index 1108fcb..bdede4f 100644
--- a/docs/public.ecr.aws/ubuntu/grafana.md
+++ b/docs/public.ecr.aws/ubuntu/grafana.md
@@ -1,6 +1,7 @@
 # Grafana™ software | Ubuntu
 
-Current Grafana™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Grafana™ software or Ubuntu release.
+Current Grafana™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Grafana™ software and Ubuntu.
 
 ## About Grafana™ software
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/grafana`. [Request 
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -76,8 +82,8 @@ docker exec -it grafana-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[datasource.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
-[grafana-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/grafana:8.1-21.10`), then:
+[datasource.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml?h=8.2-22.04), [dashboard.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml?h=8.2-22.04), [system-stats-dashboard.json](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json?h=8.2-22.04) and
+[grafana-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml?h=8.2-22.04) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/grafana:8.1-21.10`), then:
 
 ```sh
 kubectl create configmap grafana-config --from-file=grafana-datasource=datasource.yml --from-file=grafana-dashboard-definition=dashboard.yml --from-file=grafana-dashboard=system-stats-dashboard.json
diff --git a/docs/public.ecr.aws/ubuntu/kafka.md b/docs/public.ecr.aws/ubuntu/kafka.md
index 59a4554..761c2bb 100644
--- a/docs/public.ecr.aws/ubuntu/kafka.md
+++ b/docs/public.ecr.aws/ubuntu/kafka.md
@@ -1,6 +1,7 @@
 # Apache Kafka | Ubuntu
 
-Current Apache Kafka Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache Kafka or Ubuntu release.
+Current Apache Kafka Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache Kafka and Ubuntu.
 
 ## About Apache Kafka
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/kafka`. [Request ac
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -77,7 +83,7 @@ docker exec -it kafka-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[kafka-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/kafka:3.1-22.04_beta`), then:
+[kafka-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.kafka.image` in `kafka-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/kafka:3.1-22.04_beta`), then:
 
 ```sh
 kubectl apply -f kafka-deployment.yml
diff --git a/docs/public.ecr.aws/ubuntu/loki.md b/docs/public.ecr.aws/ubuntu/loki.md
index 4346232..11adcdd 100644
--- a/docs/public.ecr.aws/ubuntu/loki.md
+++ b/docs/public.ecr.aws/ubuntu/loki.md
@@ -1,6 +1,7 @@
 # Grafana Loki™ software | Ubuntu
 
-Current Grafana Loki™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Grafana Loki™ software or Ubuntu release.
+Current Grafana Loki™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Grafana Loki™ software and Ubuntu.
 
 ## About Grafana Loki™ software
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/loki`. [Request acc
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -49,7 +55,7 @@ You can now use your Loki instance exposed at `http://localhost:3100`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 3100:3100` | Expose Grafana Loki on `localhost:3100`. |
-| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
+| `-v /local/path/to/config:/etc/loki/local-config.yaml` | Local Loki Promtail config file. Can be changed using CMD `--config.file=` argument. See an [example file](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config.yaml?h=2.4-22.04). |
 | `-v lokidata:/loki` | Persist data in a docker volume named `lokidata`. |
 
 
@@ -73,8 +79,8 @@ docker exec -it loki-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[promtail-local-config-k8s.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
-[loki-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/loki:2.4-22.04_beta`), then:
+[promtail-local-config-k8s.yaml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/config/promtail-local-config-k8s.yaml?h=2.4-22.04) and
+[loki-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/loki/plain/examples/loki-deployment.yml?h=2.4-22.04) and set `containers.loki.image` in `loki-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/loki:2.4-22.04_beta`), then:
 
 ```sh
 kubectl create configmap promtail-config --from-file=promtail=promtail-local-config-k8s.yaml
diff --git a/docs/public.ecr.aws/ubuntu/memcached.md b/docs/public.ecr.aws/ubuntu/memcached.md
index 213ef3c..9791e8b 100644
--- a/docs/public.ecr.aws/ubuntu/memcached.md
+++ b/docs/public.ecr.aws/ubuntu/memcached.md
@@ -1,6 +1,7 @@
 # Memcached | Ubuntu
 
-Current Memcached Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Memcached or Ubuntu release.
+Current Memcached Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Memcached and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/memcached](https://gallery.ecr.aws/lts/memcached).
 
 ## About Memcached
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/memcached`. [Reques
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`1.6-22.04_beta`** &nbsp;&nbsp; | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/memcached) | [](https://gallery.ecr.aws/lts/memcached) | Memcached 1.6 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.6-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/memcached) | [](https://gallery.ecr.aws/lts/memcached) | Memcached 1.6.9 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/memcached but are shown here for completeness:_
@@ -29,7 +29,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/memcached but are
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -40,7 +45,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.6-21.04~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.6-21.10_beta |
+ | ~~1.6-21.10~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.6-22.04_beta |
+ | ~~1.6-21.04~~ | Memcached 1.6.9 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.6-21.10~~ |
 | _`track`_ |
 
 
@@ -49,7 +55,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name memcached-container -e TZ=UTC  public.ecr.aws/ubuntu/memcached:1.6-21.04
+docker run -d --name memcached-container -e TZ=UTC  public.ecr.aws/ubuntu/memcached:1.6-21.10
 ```
 
 #### Parameters
@@ -114,7 +120,7 @@ In this case you can append the flags themselves or a shell script to the run co
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[memcached-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/memcached:1.6-21.04`), then:
+[memcached-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml?h=1.6-22.04) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/memcached:1.6-21.10`), then:
 
 ```sh
 kubectl apply -f memcached-deployment.yml
diff --git a/docs/public.ecr.aws/ubuntu/mysql.md b/docs/public.ecr.aws/ubuntu/mysql.md
index 42fe55e..cfb5213 100644
--- a/docs/public.ecr.aws/ubuntu/mysql.md
+++ b/docs/public.ecr.aws/ubuntu/mysql.md
@@ -1,6 +1,7 @@
 # MySQL™ software | Ubuntu
 
-Current MySQL™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer MySQL™ software or Ubuntu release.
+Current MySQL™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of MySQL™ software and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/mysql](https://gallery.ecr.aws/lts/mysql).
 
 ## About MySQL™ software
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/mysql`. [Request ac
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`8.0-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/mysql) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/mysql) | MySQL™ software 8.0 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `8.0-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/mysql) | [](https://gallery.ecr.aws/lts/mysql) | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/mysql but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/mysql but are sho
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,7 +46,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~8.0-21.04~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 8.0-21.10_beta |
+ | ~~8.0-21.10~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 8.0-22.04_beta |
+ | ~~8.0-21.04~~ | MySQL™ software 8.0.27 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~8.0-21.10~~ |
 | _`track`_ |
 
 
@@ -50,7 +56,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name mysql-container -e TZ=UTC -p 30306:3306 -e MYSQL_ROOT_PASSWORD=My:S3cr3t/ public.ecr.aws/ubuntu/mysql:8.0-21.04
+docker run -d --name mysql-container -e TZ=UTC -p 30306:3306 -e MYSQL_ROOT_PASSWORD=My:S3cr3t/ public.ecr.aws/ubuntu/mysql:8.0-21.10
 ```
 Access your MySQL server at `localhost:30306`.
 
@@ -69,7 +75,7 @@ Access your MySQL server at `localhost:30306`.
 | `-e MYSQL_INITSB_SKIP_TZINFO=yes` | Timezone data is automatically loaded via entrypoint script, set this variable to any non-empty value to disable it. |
 | `-p 30306:3306` | Expose MySQL server on `localhost:30306`. |
 | `-v /path/to/data:/var/lib/mysql` | Persist data instead of initializing a new database every time you launch a new container. |
-| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
+| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04)). |
 
 #### Initialization Scripts
 
@@ -101,7 +107,7 @@ This image also includes the `mysql` client for interactive container use:
 ```sh
 $ docker network create mysql-network
 $ docker network connect mysql-network mysql-container
-$ docker run -it --rm --network mysql-network public.ecr.aws/ubuntu/mysql:8.0-21.04 mysql -hmysql-container -uroot -p
+$ docker run -it --rm --network mysql-network public.ecr.aws/ubuntu/mysql:8.0-21.10 mysql -hmysql-container -uroot -p
 ```
 The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged in and can enjoy your new instance.
 
@@ -110,8 +116,8 @@ The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[my-custom.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
-[mysql-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/mysql:8.0-21.04`), then:
+[my-custom.cnf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf?h=8.0-22.04) and
+[mysql-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml?h=8.0-22.04) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/mysql:8.0-21.10`), then:
 
 ```sh
 kubectl create configmap mysql-config --from-file=main-config=my-custom.cnf
diff --git a/docs/public.ecr.aws/ubuntu/nginx.md b/docs/public.ecr.aws/ubuntu/nginx.md
index e34f14b..b8f0bd3 100644
--- a/docs/public.ecr.aws/ubuntu/nginx.md
+++ b/docs/public.ecr.aws/ubuntu/nginx.md
@@ -1,6 +1,7 @@
 # Nginx | Ubuntu
 
-Current Nginx Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Nginx or Ubuntu release.
+Current Nginx Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Nginx and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/nginx](https://gallery.ecr.aws/lts/nginx).
 
 ## About Nginx
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/nginx`. [Request ac
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`1.18-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/nginx) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/nginx) | Nginx 1.18 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.18-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/nginx) | [](https://gallery.ecr.aws/lts/nginx) | Nginx 1.18.0 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/nginx but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/nginx but are sho
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,7 +46,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.18-21.04~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.18-21.10_beta |
+ | ~~1.18-21.10~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.18-22.04_beta |
+ | ~~1.18-21.04~~ | Nginx 1.18.0 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.18-21.10~~ |
 | _`track`_ |
 
 
@@ -50,7 +56,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name nginx-container -e TZ=UTC -p 8080:80 public.ecr.aws/ubuntu/nginx:1.18-21.04
+docker run -d --name nginx-container -e TZ=UTC -p 8080:80 public.ecr.aws/ubuntu/nginx:1.18-21.10
 ```
 Access your Nginx server at `http://localhost:8080`.
 
@@ -62,7 +68,7 @@ Access your Nginx server at `http://localhost:8080`.
 | `-p 8080:80` | Expose Nginx on `localhost:8080`. |
 | `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
 | `-v /path/to/conf.template:/etc/nginx/templates/conf.template` | Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`). |
-| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
+| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04)). |
 
 
 #### Testing/Debugging
@@ -85,8 +91,8 @@ docker exec -it nginx-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[nginx.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
-[nginx-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/nginx:1.18-21.04`), then:
+[nginx.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf?h=1.18-22.04), [index.html](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html?h=1.18-22.04) and
+[nginx-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml?h=1.18-22.04) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/nginx:1.18-21.10`), then:
 
 ```sh
 kubectl create configmap nginx-config --from-file=nginx=nginx.conf --from-file=nginx-site=index.html
diff --git a/docs/public.ecr.aws/ubuntu/postgres.md b/docs/public.ecr.aws/ubuntu/postgres.md
index 9981a38..63c6a58 100644
--- a/docs/public.ecr.aws/ubuntu/postgres.md
+++ b/docs/public.ecr.aws/ubuntu/postgres.md
@@ -1,6 +1,7 @@
 # Postgres | Ubuntu
 
-Current Postgres Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Postgres or Ubuntu release.
+Current Postgres Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Postgres and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/postgres](https://gallery.ecr.aws/lts/postgres).
 
 ## About Postgres
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/postgres`. [Request
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`14-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/postgres) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/postgres) | Postgres 14 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `13-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/postgres) | [](https://gallery.ecr.aws/lts/postgres) | Postgres 13.1 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/postgres but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/postgres but are 
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,6 +46,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~13-21.10~~ | Postgres 13.1 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 14-22.04_beta |
  | ~~13-21.04~~ | Postgres 13.1 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~13.1-21.10~~ |
 | _`track`_ |
 
@@ -50,7 +56,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name postgres-container -e TZ=UTC -p 30432:5432 -e POSTGRES_PASSWORD=My:s3Cr3t/ public.ecr.aws/ubuntu/postgres:13-21.04
+docker run -d --name postgres-container -e TZ=UTC -p 30432:5432 -e POSTGRES_PASSWORD=My:s3Cr3t/ public.ecr.aws/ubuntu/postgres:13-21.10
 ```
 Access your PostgreSQL server at `localhost:30432`.
 
@@ -67,7 +73,7 @@ Access your PostgreSQL server at `localhost:30432`.
 | `-e POSTGRES_HOST_AUTH_METHOD=trust` | Set the `auth-method` for `host` connections for `all` databases, `all` users, and `all` addresses. The following will be added to the `pg_hba.conf` if this option is passed: `host all all all $POSTGRES_HOST_AUTH_METHOD`. |
 | `-e PGDATA=/path/to/location` | Set the location of the database files. The default is `/var/lib/postgresql/data`. |
 | `-p 30432:5432` | Expose Postgres on `localhost:30432`. |
-| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
+| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04)). |
 | `-v /path/to/persisted/data:/var/lib/postgresql/data` | Persist data instead of initializing a new database every time you launch a new container. |
 
 #### Initialization Scripts
@@ -100,7 +106,7 @@ This image also includes the `psql` client for interactive container use:
 ```sh
 $ docker network create postgres-network
 $ docker network connect postgres-network postgres-container
-$ docker run -it --rm --network postgres-network public.ecr.aws/ubuntu/postgres:13-21.04 psql -h postgres-container -U postgres
+$ docker run -it --rm --network postgres-network public.ecr.aws/ubuntu/postgres:13-21.10 psql -h postgres-container -U postgres
 ```
 The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged in and can enjoy your new instance.
 
@@ -109,8 +115,8 @@ The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged i
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[postgresql.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
-[postgres-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/postgres:13-21.04`), then:
+[postgresql.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf?h=14-22.04) and
+[postgres-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml?h=14-22.04) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/postgres:13-21.10`), then:
 
 ```sh
 kubectl create configmap postgres-config --from-file=main-config=postgresql.conf
diff --git a/docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md b/docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md
index a5b1127..2937695 100644
--- a/docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md
+++ b/docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md
@@ -1,6 +1,7 @@
 # Prometheus Alertmanager | Ubuntu
 
-Current Prometheus Alertmanager Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Prometheus Alertmanager or Ubuntu release.
+Current Prometheus Alertmanager Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Prometheus Alertmanager and Ubuntu.
 
 ## About Prometheus Alertmanager
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/prometheus-alertman
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -52,7 +58,7 @@ Access your Prometheus Alertmanager server at `localhost:30093`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30093:9093` | Expose Prometheus Alertmanager on `localhost:30093`. |
-| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
+| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04)). |
 | `-v /path/to/persisted/data:/alertmanager` | Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container. |
 
 
@@ -76,8 +82,8 @@ docker exec -it prometheus-alertmanager-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[alertmanager.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
-[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/prometheus-alertmanager:0.22-21.10`), then:
+[alertmanager.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/config/alertmanager.yml?h=0.23-22.04) and
+[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus-alertmanager/plain/examples/alertmanager-deployment.yml?h=0.23-22.04) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/prometheus-alertmanager:0.22-21.10`), then:
 
 ```sh
 kubectl create configmap alertmanager-config --from-file=alertmanager=alertmanager.yml
diff --git a/docs/public.ecr.aws/ubuntu/prometheus.md b/docs/public.ecr.aws/ubuntu/prometheus.md
index 278d4d4..cbfe9a1 100644
--- a/docs/public.ecr.aws/ubuntu/prometheus.md
+++ b/docs/public.ecr.aws/ubuntu/prometheus.md
@@ -1,6 +1,7 @@
 # Prometheus | Ubuntu
 
-Current Prometheus Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Prometheus or Ubuntu release.
+Current Prometheus Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Prometheus and Ubuntu.
 
 ## About Prometheus
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/prometheus`. [Reque
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -53,8 +59,8 @@ Access your Prometheus server at `localhost:30090`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30090:9090` | Expose Prometheus server on `localhost:30090`. |
-| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
-| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
+| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04)). |
+| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04)). |
 
 
 #### Testing/Debugging
@@ -77,8 +83,8 @@ docker exec -it prometheus-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[prometheus.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
-[prometheus-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/prometheus:2.28-21.10`), then:
+[prometheus.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/prometheus.yml?h=2.33-22.04), [alerts.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/config/alerts.yml?h=2.33-22.04) and
+[prometheus-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/prometheus/plain/examples/prometheus-deployment.yml?h=2.33-22.04) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/prometheus:2.28-21.10`), then:
 
 ```sh
 kubectl create configmap prometheus-config --from-file=prometheus=prometheus.yml --from-file=prometheus-alerts=alerts.yml
diff --git a/docs/public.ecr.aws/ubuntu/redis.md b/docs/public.ecr.aws/ubuntu/redis.md
index 3d92bd8..83e0972 100644
--- a/docs/public.ecr.aws/ubuntu/redis.md
+++ b/docs/public.ecr.aws/ubuntu/redis.md
@@ -1,6 +1,7 @@
 # Redis™ software | Ubuntu
 
-Current Redis™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Redis™ software or Ubuntu release.
+Current Redis™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Redis™ software and Ubuntu.
 
 ## About Redis™ software
 
@@ -17,11 +18,15 @@ Up to 10 years customer security maintenance `from canonical/redis`. [Request ac
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`6.2-22.04_beta`** &nbsp;&nbsp; | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/redis) | [](https://gallery.ecr.aws/lts/redis) | Redis™ software 6.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `6.0-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/redis) | [](https://gallery.ecr.aws/lts/redis) | Redis™ software 6.0.15 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -32,7 +37,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~6.0-21.04~~ | Redis™ software 6.0.11 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 6.0-21.10_beta |
+ | ~~6.0-21.10~~ | Redis™ software 6.0.15 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 6.2-22.04_beta |
+ | ~~6.0-21.04~~ | Redis™ software 6.0.11 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~6.0-21.10~~ |
  | ~~5.0-20.04~~ | Redis™ software 5.0.7 on Ubuntu&nbsp;20.04&nbsp;LTS | 01/2021 | ~~6.0-21.04~~ |
 | _`track`_ |
 
@@ -42,7 +48,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name redis-container -e TZ=UTC -p 30073:6379 -e REDIS_PASSWORD=mypassword public.ecr.aws/ubuntu/redis:6.0-21.04
+docker run -d --name redis-container -e TZ=UTC -p 30073:6379 -e REDIS_PASSWORD=mypassword public.ecr.aws/ubuntu/redis:6.0-21.10
 ```
 Access your Redis server at `localhost:30073`.
 
@@ -57,7 +63,7 @@ Access your Redis server at `localhost:30073`.
 | `-e REDIS_ALLOW_REMOTE_CONNECTIONS=yes` | Set to `no` to disallow remote connections to `redis-server` (i.e., make `redis-server` listen to `127.0.0.1` only). |
 | `-e REDIS_EXTRA_FLAGS` | Specify extra flags to be passed to `redis-server` when initializing it. |
 | `-p 30073:6379` | Expose redis on `localhost:30073`. |
-| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
+| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04)). **To enable TLS** mode, comment the `port 6379` line and uncomment the `# port 0` and `# tls-port 6379` lines.
  |
 
 
@@ -80,7 +86,7 @@ This image also includes the `redis-cli` client for interactive container use:
 ```sh
 $ docker network create redis-network
 $ docker network connect redis-network redis-container
-$ docker run -it --rm --network redis-network public.ecr.aws/ubuntu/redis:6.0-21.04 redis-cli -h redis-container
+$ docker run -it --rm --network redis-network public.ecr.aws/ubuntu/redis:6.0-21.10 redis-cli -h redis-container
 ```
 Now you can:
 ```
@@ -97,8 +103,8 @@ redis:6379>
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[redis.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
-[redis-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/redis:6.0-21.04`), then:
+[redis.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf?h=6.2-22.04) and
+[redis-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml?h=6.2-22.04) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/redis:6.0-21.10`), then:
 
 ```sh
 kubectl create configmap redis-config --from-file=redis=redis.conf
diff --git a/docs/public.ecr.aws/ubuntu/squid.md b/docs/public.ecr.aws/ubuntu/squid.md
index 41443da..0e307eb 100644
--- a/docs/public.ecr.aws/ubuntu/squid.md
+++ b/docs/public.ecr.aws/ubuntu/squid.md
@@ -1,6 +1,7 @@
 # Squid | Ubuntu
 
-Current Squid Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Squid or Ubuntu release.
+Current Squid Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Squid and Ubuntu.
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/squid](https://gallery.ecr.aws/lts/squid).
 
 ## About Squid
@@ -18,7 +19,6 @@ Up to 10 years customer security maintenance `from canonical/squid`. [Request ac
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | _**`5.2-22.04_beta`** &nbsp;&nbsp;_ | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/squid) | [![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)](https://gallery.ecr.aws/lts/squid) | Squid 5.2 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `4.13-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/squid) | [](https://gallery.ecr.aws/lts/squid) | Squid 4.13 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 _The following tags are not available in public.ecr.aws/ubuntu/squid but are shown here for completeness:_
@@ -30,7 +30,12 @@ _The following tags are not available in public.ecr.aws/ubuntu/squid but are sho
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -41,6 +46,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
+ | ~~4.13-21.10~~ | Squid 4.13 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 5.2-22.04_beta |
 | _`track`_ |
 
 
@@ -49,7 +55,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name squid-container -e TZ=UTC -p 3128:3128 public.ecr.aws/ubuntu/squid:5.2-22.04_beta
+docker run -d --name squid-container -e TZ=UTC -p 3128:3128 public.ecr.aws/ubuntu/squid:4.13-21.10
 ```
 Access your Squid proxy at `localhost:3128`.
 
@@ -85,8 +91,8 @@ docker exec -it squid-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[squid.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
-[squid-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/squid:5.2-22.04_beta`), then:
+[squid.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/config/squid.conf?h=5.2-22.04) and
+[squid-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/squid/plain/examples/squid-deployment.yml?h=5.2-22.04) and set `containers.squid.image` in `squid-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/squid:4.13-21.10`), then:
 
 ```sh
 kubectl create configmap squid-config --from-file=squid=squid.conf
diff --git a/docs/public.ecr.aws/ubuntu/telegraf.md b/docs/public.ecr.aws/ubuntu/telegraf.md
index 533a1a6..96faf25 100644
--- a/docs/public.ecr.aws/ubuntu/telegraf.md
+++ b/docs/public.ecr.aws/ubuntu/telegraf.md
@@ -1,6 +1,7 @@
 # Telegraf™ software | Ubuntu
 
-Current Telegraf™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Telegraf™ software or Ubuntu release.
+Current Telegraf™ software Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Telegraf™ software and Ubuntu.
 
 ## About Telegraf™ software
 
@@ -17,11 +18,15 @@ Up to 10 years customer security maintenance `from canonical/telegraf`. [Request
 | Channel Tag | | | Currently | Architectures |
 |---|---|---|---|---|
  | **`1.21-22.04_beta`** &nbsp;&nbsp; | [![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)](https://gallery.ecr.aws/lts/telegraf) | [](https://gallery.ecr.aws/lts/telegraf) | Telegraf™ software 1.21 on Ubuntu&nbsp;22.04&nbsp;LTS| `amd64`, `arm64`, `ppc64el`, `s390x` |
- | `1.19-21.10_beta` &nbsp;&nbsp; | [](https://gallery.ecr.aws/lts/telegraf) | [](https://gallery.ecr.aws/lts/telegraf) | Telegraf™ software 1.19.2 on Ubuntu&nbsp;21.10&nbsp;| `amd64`, `arm64`, `ppc64el`, `s390x` |
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -32,7 +37,8 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 
 | Track | Version | EOL | Upgrade Path |
 |---|---|---|---|
- | ~~1.17-21.04~~ | Telegraf™ software 1.17.2 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | 1.19-21.10_beta |
+ | ~~1.19-21.10~~ | Telegraf™ software 1.19.2 on Ubuntu&nbsp;21.10&nbsp; | 07/2022 | 1.21-22.04_beta |
+ | ~~1.17-21.04~~ | Telegraf™ software 1.17.2 on Ubuntu&nbsp;21.04&nbsp; | 01/2022 | ~~1.19-21.10~~ |
  | ~~1.15-20.04~~ | Telegraf™ software 1.15.2 on Ubuntu&nbsp;20.04&nbsp;LTS | 01/2021 | ~~1.17-21.04~~ |
 | _`track`_ |
 
@@ -42,7 +48,7 @@ These channels (tags) are not updated anymore. Please upgrade to newer channels,
 Launch this image locally:
 
 ```sh
-docker run -d --name telegraf-container -e TZ=UTC -p 30273:9273 public.ecr.aws/ubuntu/telegraf:1.17-21.04
+docker run -d --name telegraf-container -e TZ=UTC -p 30273:9273 public.ecr.aws/ubuntu/telegraf:1.19-21.10
 ```
 Access your Telegraf server at `localhost:30273`.
 
@@ -52,7 +58,7 @@ Access your Telegraf server at `localhost:30273`.
 |---|---|
 | `-e TZ=UTC` | Timezone. |
 | `-p 30273:9273` | Expose Telegraf on `localhost:30273`. |
-| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
+| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04)). |
 
 
 #### Testing/Debugging
@@ -75,8 +81,8 @@ docker exec -it telegraf-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[telegraf.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
-[telegraf-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/telegraf:1.17-21.04`), then:
+[telegraf.conf](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf?h=1.21-22.04) and
+[telegraf-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml?h=1.21-22.04) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/telegraf:1.19-21.10`), then:
 
 ```sh
 kubectl create configmap telegraf-config --from-file=main-config=telegraf.conf
diff --git a/docs/public.ecr.aws/ubuntu/zookeeper.md b/docs/public.ecr.aws/ubuntu/zookeeper.md
index 36065d1..f3bfa03 100644
--- a/docs/public.ecr.aws/ubuntu/zookeeper.md
+++ b/docs/public.ecr.aws/ubuntu/zookeeper.md
@@ -1,6 +1,7 @@
 # Apache ZooKeeper | Ubuntu
 
-Current Apache ZooKeeper Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer Apache ZooKeeper or Ubuntu release.
+Current Apache ZooKeeper Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of Apache ZooKeeper and Ubuntu.
 
 ## About Apache ZooKeeper
 
@@ -20,7 +21,12 @@ Up to 10 years customer security maintenance `from canonical/zookeeper`. [Reques
 | _`track_risk`_ |
 
 
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
 
 
 ### Commercial use and Extended Security Maintenance channels
@@ -72,7 +78,7 @@ docker exec -it zookeeper-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[zookeeper-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/zookeeper:3.1-22.04_beta`), then:
+[zookeeper-deployment.yml](https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/kafka/plain/examples/kafka-deployment.yml?h=3.1-22.04) and set `containers.zookeeper.image` in `zookeeper-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/zookeeper:3.1-22.04_beta`), then:
 
 ```sh
 kubectl apply -f zookeeper-deployment.yml
diff --git a/templates/README_DOCKERHUB.md b/templates/README_DOCKERHUB.md
index 5456979..2c756cd 100644
--- a/templates/README_DOCKERHUB.md
+++ b/templates/README_DOCKERHUB.md
@@ -1,6 +1,9 @@
 # ${application} | Ubuntu
 
-Current ${application} Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer ${application} or Ubuntu release. **This repository is free to use and exempted from per-user rate limits.**
+Current ${application} Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of ${application} and Ubuntu.
+**This repository is free to use and exempted from per-user rate limits.**
+
 <%
     baserepo='ubuntu'
     tag='latest'
diff --git a/templates/README_ECR.md b/templates/README_ECR.md
index 5a9b435..8a82ba7 100644
--- a/templates/README_ECR.md
+++ b/templates/README_ECR.md
@@ -13,7 +13,8 @@
     current_releases=[current_releases.pop(0)]+[release for release in current_releases if release not in lts_releases]
     has_an_lts=len(lts_releases)>0
 %>
-Current ${application} Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu. Receives security updates and rolls to newer ${application} or Ubuntu release.
+Current ${application} Docker Image [from Canonical](https://ubuntu.com/security/docker-images), based on Ubuntu.
+Receives security updates and tracks the newest combination of ${application} and Ubuntu.
 % if has_an_lts:
 For [long-term support (LTS)](https://ubuntu.com/security/docker-images) versions of this image, see [public.ecr.aws/lts/${repo}](https://gallery.ecr.aws/lts/${repo}).
 % endif
diff --git a/templates/channels_message.md b/templates/channels_message.md
index 3901cf9..e2c918f 100644
--- a/templates/channels_message.md
+++ b/templates/channels_message.md
@@ -1 +1,6 @@
-Channel Tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
+Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg `1.0-22.04`.
+Channels are ordered from the most stable to the least `stable`, `candidate`, `beta`, `edge`.
+More risky channels are always implicitly available.
+So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull `beta` and `edge`.
+When `stable` is listed, all four are available.
+Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.