Add canary deploys

The auto-deploy changes will be linked.

autodeploy/Kubernetes.gitlab-ci.yml

@@ -11,6 +11,7 @@ stages:
   - test
   - review
   - staging
+  - canary
   - production
   - cleanup
@@ -21,23 +22,32 @@ build:
   only:
     - branches
+canary:
+  stage: canary
+  script:
+    - command canary
+  environment:
+    name: production
+    url: http://$CI_PROJECT_NAME.$KUBE_DOMAIN
+  when: manual
+  allow_failure: false
+  only:
+    - master
+
 production:
   stage: production
-  variables:
-    CI_ENVIRONMENT_URL: http://$CI_PROJECT_NAME.$KUBE_DOMAIN
   script:
     - command deploy
   environment:
     name: production
     url: http://$CI_PROJECT_NAME.$KUBE_DOMAIN
   when: manual
+  allow_failure: false
   only:
     - master
 staging:
   stage: staging
-  variables:
-    CI_ENVIRONMENT_URL: http://$CI_PROJECT_NAME-staging.$KUBE_DOMAIN
   script:
     - command deploy
   environment:
@@ -48,8 +58,6 @@ staging:
 review:
   stage: review
-  variables:
-    CI_ENVIRONMENT_URL: http://$CI_PROJECT_NAME-$CI_ENVIRONMENT_SLUG.$KUBE_DOMAIN
   script:
     - command deploy
   environment:
@@ -71,6 +79,7 @@ stop_review:
     name: review/$CI_COMMIT_REF_NAME
     action: stop
   when: manual
+  allow_failure: true
   only:
     - branches
   except:

[Mark Pundsack]

@ayufan This makes canaries part of every auto deploy, even for GitLab CE. Are we sure we want to do that? Can we have a different template for CE vs EE? I mean, it's not horrible to do it this way. But it means we're giving some level of canary deploy support to CE, and only visualization of canary deploys to EEP. /cc @JobV

[🚄 Job van der Voort 🚀]

Canaries are available anyway in CE? If so, I can't object using them. As long as part of it is exclusive to EEP..

[Zeger-Jan van de Weg]

Isn't this implicit?

[Mark Pundsack]

@zj Manual jobs default to allow_failure: true, iirc

[Mark Pundsack]

@ayufan Shouldn't this be CI_COMMIT_REF_SLUG?