update install command to 1.31 candidate

canonical · Nov 27, 2024 · baf0f84 · baf0f84
1 parent 49ed829
commit baf0f84
Show file tree

Hide file tree

Showing 9 changed files with 12 additions and 22 deletions.
diff --git a/docs/src/capi/howto/custom-ck8s.md b/docs/src/capi/howto/custom-ck8s.md
@@ -31,13 +31,13 @@ spec:
     files:
     - content: |
         #!/bin/bash -xe
-        snap install k8s --classic --channel=latest/edge
+        snap install k8s --classic --channel=1.31-classic/candidate
       owner: root:root
       path: /capi/scripts/install.sh
       permissions: "0500"
 ```
 
-Now the new control plane nodes that are created using this manifest will have the `latest/edge` {{product}} snap installed on them!
+Now the new control plane nodes that are created using this manifest will have the `1.31-classic/candidate` {{product}} snap installed on them!
 
 ## Use `preRunCommands`
 
@@ -57,7 +57,7 @@ spec:
   ...
   spec:
     preRunCommands:
-    - snap install k8s --classic --channel=latest/edge
+    - snap install k8s --classic --channel=1.31-classic/candidate
 ```
 
 <!-- LINKS -->

diff --git a/docs/src/capi/tutorial/getting-started.md b/docs/src/capi/tutorial/getting-started.md
@@ -39,7 +39,7 @@ The management cluster hosts the CAPI providers. You can use {{product}} as a
 management cluster:
 
 ```
-sudo snap install k8s --classic --edge
+sudo snap install k8s --classic --channel=1.31-classic/candidate
 sudo k8s bootstrap
 sudo k8s status --wait-ready
 mkdir -p ~/.kube/

diff --git a/docs/src/charm/howto/charm.md b/docs/src/charm/howto/charm.md
@@ -38,12 +38,7 @@ page][channels] for an explanation of the different types of channel.
 The charm can be installed with the `juju` command:
 
 ```
-juju deploy k8s --channel=latest/edge
-```
-
-```{note}
-The `latest/edge` channel is always under active development. This is where you
-will find the latest features but you may also experience instability.
+juju deploy k8s --channel=1.31/candidate
 ```
 
 ## Bootstrap the cluster

diff --git a/docs/src/charm/tutorial/getting-started.md b/docs/src/charm/tutorial/getting-started.md
@@ -68,7 +68,7 @@ recommendation is two CPU cores, 16GB of memory and 40GB of disk space. Now we
 can go ahead and create a cluster:
 
 ```
-juju deploy k8s --channel=latest/edge --constraints='cores=2 mem=16G root-disk=40G'
+juju deploy k8s --channel=1.31/candidate --constraints='cores=2 mem=16G root-disk=40G'
 ```
 
 At this point Juju will fetch the charm from Charmhub, create a new instance
@@ -97,7 +97,7 @@ more of its resources are available for running workloads. We can deploy a
 worker node in a similar way to the original K8s node:
 
 ```
-juju deploy k8s-worker --channel=latest/edge --constraints='cores=2 mem=16G root-disk=40G'
+juju deploy k8s-worker --channel=latest/candidate --constraints='cores=2 mem=16G root-disk=40G'
 ```
 
 Once again, this will take a few minutes. In this case though, the `k8s-worker`

diff --git a/docs/src/snap/howto/install/lxd.md b/docs/src/snap/howto/install/lxd.md
@@ -65,7 +65,7 @@ also applying the `k8s` profile - the order is important.
 First, we’ll need to install {{product}} within the container.
 
 ```
-lxc exec k8s -- sudo snap install k8s --classic --channel=latest/edge
+lxc exec k8s -- sudo snap install k8s --classic --channel=1.31-classic/candidate
 ```
 
 ```{note}

diff --git a/docs/src/snap/howto/install/offline.md b/docs/src/snap/howto/install/offline.md
@@ -19,7 +19,7 @@ From a machine with access to the internet download the
 `k8s` and `core20` snap with:
 
 ```
-sudo snap download k8s --channel 1.30-classic/beta --basename k8s
+sudo snap download k8s --channel 1.31-classic/candidate --basename k8s
 sudo snap download core20 --basename core20
 ```
 

diff --git a/docs/src/snap/howto/install/snap.md b/docs/src/snap/howto/install/snap.md
@@ -37,12 +37,7 @@ page] for an explanation of the different types of channel.
 The snap can be installed with the snap command:
 
 ```
-sudo snap install k8s --classic --channel=latest/edge
-```
-
-```{note}
-The `latest/edge` channel is always under active development. This is where you
-will find the latest features but you may also experience instability.
+sudo snap install k8s --classic --channel=1.31-classic/candidate
 ```
 
 ## Bootstrap the cluster

diff --git a/docs/src/snap/tutorial/add-remove-nodes.md b/docs/src/snap/tutorial/add-remove-nodes.md
@@ -48,7 +48,7 @@ run commands.
 Install {{product}} on both VMs with the following command:
 
 ```
-sudo snap install --classic --edge k8s
+sudo snap install k8s --classic --channel=1.31-classic/candidate 
 ```
 <!-- markdownlint-capture -->
 <!-- markdownlint-disable -->

diff --git a/docs/src/snap/tutorial/getting-started.md b/docs/src/snap/tutorial/getting-started.md
@@ -20,7 +20,7 @@ installation.
 Install the {{product}} snap with:
 
 ```
-sudo snap install k8s --edge --classic
+sudo snap install k8s --classic --channel=1.31-classic/candidate 
 ```
 
 ### 2. Bootstrap a Kubernetes cluster