feat: Canary triggered on canary track only

Previously the canary behaviour to disable service and ingress was
triggered on non-stable tracks. Now this behaviour is triggered
explicitly only on canary tracks.

README.md

@@ -74,7 +74,7 @@ jobs:
 
 ## Example canary
 
-If a track is chosen that is not equal to stable, this updates the helm chart
+If a track is chosen that is equal to canary, this updates the helm chart
 in a few ways:
 
 1. Release name is changed to `{release}-{track}` (eg. myapp-canary).
@@ -108,4 +108,3 @@ jobs:
       env:
         KUBECONFIG_FILE: '${{ secrets.KUBECONFIG }}'
 ```
-

index.js

@@ -180,9 +180,10 @@ async function run() {
     if (version) args.push(`--set=app.version=${version}`);
     valueFiles.forEach(f => args.push(`--values=${f}`));
 
-    // Stable track only deploys service and ingress resources. Any other track
-    // name can be treated like a canary deployment.
-    if (track !== "stable") {
+    // Special behaviour is triggered if the track is labelled 'canary'. The
+    // service and ingress resources are disabled. Access to the canary
+    // deployments can be routed via the main stable service resource.
+    if (track === "canary") {
       args.push("--set=service.enabled=false", "--set=ingress.enabled=false");
     }