Doc changes for release 1.20

config.toml

@@ -110,7 +110,7 @@ algolia_docsearch = true
 # current release branch - could be rc
 release_branch = "main"
 # the main version. Never is rc.
-release_version = "v1.19.0"
+release_version = "v1.20.0"
 
 slackurl = "/slack"
 

content/en/docs/architecture/controller.md

@@ -5,6 +5,7 @@ description: >
   Accept REST API requests and create Fission resources
 ---
 
+
 {{< notice info >}}
 Controller is deprecated from version 1.18.0. You can still enable it using - `controller.enabled` flag in helm charts.
 {{< /notice >}}

content/en/docs/installation/_index.en.md

@@ -17,7 +17,7 @@ If you already have Helm, [skip ahead to the fission install](#install-fission).
 If you don't have a Kubernetes cluster, [here's a official guide to set one up](https://kubernetes.io/docs/setup/).
 
 {{< notice info >}}
-Fission requires Kubernetes 1.19 or higher
+Fission requires Kubernetes 1.23 or higher
 {{< /notice >}}
 
 ### Kubectl

content/en/docs/installation/env_vars.en.md

@@ -29,11 +29,11 @@ You don't need to set this if you're simply running `fission function test --nam
 {{% /notice %}}
 
 {{% notice warning %}}
-Fission CLI uses value in `FISSION_ROUTER` if it's not empty instead of using local port-forward mechanism.</br>
+Fission CLI uses value in `FISSION_ROUTER_URL` if it's not empty instead of using local port-forward mechanism.</br>
 You need to ensure that the IP address in it is **accessible** from the public network.
 {{% /notice %}}
 
-It's convenient to set the `FISSION_ROUTER` environment variable to the **externally-visible** address of the Fission router.
+It's convenient to set the `FISSION_ROUTER_URL` environment variable to the **externally-visible** address of the Fission router.
 
 ### Clusters Only Support NodePort
 

content/en/docs/releases/v1.20.0-rc2.md → content/en/docs/releases/v1.20.0.md

@@ -1,6 +1,6 @@
 ---
-title: "v1.20.0-rc2"
-linkTitle: v1.20.0-rc2
+title: "v1.20.0"
+linkTitle: v1.20.0
 weight: 77
 ---
 

content/en/docs/usage/triggers/message-queue-trigger/_index.md

@@ -1,11 +1,12 @@
 ---
-title: "[Deprecated] Message Queue Trigger: Kind Fission"
+title: "[Removed] Message Queue Trigger: Kind Fission"
 date: 2019-12-17T14:38:11+08:00
 weight: 4
+draft: true
 ---
 
 {{% alert title="Note" color="warning" %}}
-Message Queue Trigger with kind Fission are deprecated, we suggest using [MQ Trigger with Keda](/docs/usage/triggers/message-queue-trigger-kind-keda/) instead.
+Message Queue Trigger with kind Fission is removed from 1.20 release, we suggest using [MQ Trigger with Keda](/docs/usage/triggers/message-queue-trigger-kind-keda/) instead.
 {{% /alert %}}
 
 ## How Message Queue Trigger Works

netlify.toml

@@ -538,4 +538,24 @@ status = 301
 force = true
 from = "/docs/releases/v1.20.0-rc1/"
 to = "/docs/releases/v1.20.0-rc2/"
-status = 301
+status = 301
+
+[[redirects]]
+force = true
+from = "/docs/releases/v1.20.0-rc2/"
+to = "/docs/releases/v1.20.0/"
+
+[[redirects]]
+force = true
+from = "/docs/usage/triggers/message-queue-trigger/"
+to = "/docs/usage/triggers/message-queue-trigger-kind-keda/"
+
+[[redirects]]
+force = true
+from = "/docs/usage/triggers/message-queue-trigger/nats-streaming/"
+to = "/docs/usage/triggers/message-queue-trigger-kind-keda/nats-streaming/"
+
+[[redirects]]
+force = true
+from = "/docs/usage/triggers/message-queue-trigger/kafka/"
+to = "/docs/usage/triggers/message-queue-trigger-kind-keda/kafka/"