Parameterize python and controller version separately

Author: NickCao

docs/source/cli/getting-started.md

@@ -12,7 +12,11 @@ configurations, and run transient or persistent exporter instances.
 
 The `jmp` and `jmp-exporter` CLI tools are available as part of the `jumpstarter` Python package.
 You can learn how to install this package [here](../installation/python-package.md),
-but it is also available as a container image `quay.io/jumpstarter/jumpstarter:main`.
+but it is also available as a container image
+```{code-block}
+:substitutions:
+quay.io/jumpstarter/jumpstarter:{{version}}
+```
 
 To check if you have the client CLI installed, run:
 

docs/source/conf.py

@@ -46,5 +46,6 @@
 ]
 myst_substitutions = {
     "requires_python": ">=3.11",
-    "version": "0.5.0rc2",
+    "version": "0.5.0",
+    "controller_version": "0.5.0",
 }

docs/source/config.md

@@ -240,11 +240,12 @@ the network.
 
 To run the exporter container on a test runner using Podman:
 
-```bash
+```{code-block} bash
+:substitutions:
 $ sudo podman run --rm -ti --name my-exporter --net=host  --privileged \
                 -e JUMPSTARTER_GRPC_INSECURE=1 \
                 -v /run/udev:/run/udev -v /dev:/dev -v /etc/jumpstarter:/etc/jumpstarter \
-                quay.io/jumpstarter-dev/jumpstarter:main \
+                quay.io/jumpstarter-dev/jumpstarter:{{version}} \
                 jmp-exporter run my-exporter
 
 INFO:jumpstarter.exporter.exporter:Registering exporter with controller
@@ -265,15 +266,16 @@ To run the exporter as a service podman-systemd is recommended, by using podman-
 you can simply create a systemd service file at `/etc/containers/systemd/my-exporter.container` with
 the following content:
 
-```ini
+```{code-block} ini
+:substitutions:
 [Unit]
 Description=My exporter
 
 [Container]
 ContainerName=my-exporter
 Environment=JUMPSTARTER_GRPC_INSECURE=1
 Exec=jmp-exporter run my-exporter
-Image=quay.io/jumpstarter-dev/jumpstarter:main
+Image=quay.io/jumpstarter-dev/jumpstarter:{{version}}
 Network=host
 PodmanArgs=--privileged
 Volume=/run/udev:/run/udev

docs/source/installation/container-jmp.md

@@ -7,10 +7,11 @@ packages locally, you can create an alias to run the `jmp` client in a container
 It is recommended to add the alias to your shell profile.
 ```
 
-```bash
+```{code-block} bash
+:substitutions:
 $ alias jmp='podman run --rm -it -e JUMPSTARTER_GRPC_INSECURE=1 \
               -v "${HOME}/.config/jumpstarter/:/root/.config/jumpstarter" \
-               quay.io/jumpstarter-dev/jumpstarter:main jmp'
+               quay.io/jumpstarter-dev/jumpstarter:{{version}} jmp'
 ```
 
 Then you can try:
@@ -30,13 +31,14 @@ to mount access to devices into the container, provide host network access,
 and run the container in privileged mode, this probably needs to be run as **root**.
 
 
-```bash
+```{code-block} bash
+:substitutions:
 $ mkdir -p "${HOME}/.config/jumpstarter/" /etc/jumpstarter
 
 # you may want to add this alias to the profile
 $ alias jmp-exporter='podman run --rm -it -e JUMPSTARTER_GRPC_INSECURE=1 \
               -v "${HOME}/.config/jumpstarter/:/root/.config/jumpstarter" \
               --net=host  --privileged \
               -v /run/udev:/run/udev -v /dev:/dev -v /etc/jumpstarter:/etc/jumpstarter \
-              quay.io/jumpstarter-dev/jumpstarter:main jmp-exporter'
+              quay.io/jumpstarter-dev/jumpstarter:{{version}} jmp-exporter'
 ```

docs/source/installation/service-cli.md

@@ -9,7 +9,7 @@ the latest release.
 ## Installing the CLI
 ```{code-block} bash
 :substitutions:
-export VERSION={{version}}
+export VERSION={{controller_version}}
 export ARCH=amd64 # or arm64
 
 curl -L https://github.com/jumpstarter-dev/jumpstarter-controller/releases/download/${VERSION}/jmpctl_${VERSION}_linux_${ARCH} \

docs/source/installation/service/kind-helm.md

@@ -72,5 +72,5 @@ helm upgrade jumpstarter --install oci://quay.io/jumpstarter-dev/helm/jumpstarte
             --set global.metrics.enabled=false \
             --set jumpstarter-controller.grpc.nodeport.enabled=true \
             --set jumpstarter-controller.grpc.mode=nodeport \
-            --version={{version}}
+            --version={{controller_version}}
 ```

docs/source/installation/service/kubernetes-helm.md

@@ -18,5 +18,5 @@ helm upgrade jumpstarter --install oci://quay.io/jumpstarter-dev/helm/jumpstarte
         --set global.baseDomain=jumpstarter.example.com \
         --set global.metrics.enabled=true `# disable if metrics not available` \
         --set jumpstarter-controller.grpc.mode=ingress \
-        --version={{version}}
+        --version={{controller_version}}
 ```

docs/source/installation/service/minikube-helm.md

@@ -43,5 +43,5 @@ helm upgrade jumpstarter --install oci://quay.io/jumpstarter-dev/helm/jumpstarte
             --set global.metrics.enabled=false \
             --set jumpstarter-controller.grpc.nodeport.enabled=true \
             --set jumpstarter-controller.grpc.mode=nodeport \
-            --version={{version}}
+            --version={{controller_version}}
 ```

docs/source/installation/service/openshift-argocd.md

@@ -90,6 +90,6 @@ spec:
       - name: jumpstarter-controller.grpc.mode
         value: "route"
     repoURL: quay.io/jumpstarter-dev/helm
-    targetRevision: "{{version}}"
+    targetRevision: "{{controller_version}}"
 ```
 

docs/source/installation/service/openshift-helm.md

@@ -19,7 +19,7 @@ helm upgrade jumpstarter --install oci://quay.io/jumpstarter-dev/helm/jumpstarte
           --set global.baseDomain=jumpstarter.example.com \
           --set global.metrics.enabled=true \
           --set jumpstarter-controller.grpc.mode=route \
-          --version={{version}}
+          --version={{controller_version}}
 ```