This is an automated email from the ASF dual-hosted git repository.
zhangjintao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git
The following commit(s) were added to refs/heads/master by this push:
new ccdd6a2a docs: add Gateway API installation instructions (#1616)
ccdd6a2a is described below
commit ccdd6a2ab3fbfc14d14daf67c27204eb9ff43d38
Author: Navendu Pottekkat <[email protected]>
AuthorDate: Tue Jan 31 14:24:32 2023 +0530
docs: add Gateway API installation instructions (#1616)
---
docs/en/latest/deployments/ack.md | 16 ++++++++++++++++
docs/en/latest/deployments/aws.md | 16 ++++++++++++++++
docs/en/latest/deployments/azure.md | 16 ++++++++++++++++
docs/en/latest/deployments/gke.md | 16 ++++++++++++++++
docs/en/latest/deployments/k3s-rke.md | 16 ++++++++++++++++
docs/en/latest/deployments/kind.md | 16 ++++++++++++++++
docs/en/latest/deployments/kubesphere.md | 16 ++++++++++++++++
docs/en/latest/deployments/minikube.md | 16 ++++++++++++++++
docs/en/latest/deployments/tke.md | 16 ++++++++++++++++
9 files changed, 144 insertions(+)
diff --git a/docs/en/latest/deployments/ack.md
b/docs/en/latest/deployments/ack.md
index 9371b793..02d959a7 100644
--- a/docs/en/latest/deployments/ack.md
+++ b/docs/en/latest/deployments/ack.md
@@ -68,6 +68,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/aws.md
b/docs/en/latest/deployments/aws.md
index e143000e..b267879f 100644
--- a/docs/en/latest/deployments/aws.md
+++ b/docs/en/latest/deployments/aws.md
@@ -86,6 +86,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/azure.md
b/docs/en/latest/deployments/azure.md
index cfb1de57..697c3c58 100644
--- a/docs/en/latest/deployments/azure.md
+++ b/docs/en/latest/deployments/azure.md
@@ -71,6 +71,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/gke.md
b/docs/en/latest/deployments/gke.md
index 846d0992..84e341b3 100644
--- a/docs/en/latest/deployments/gke.md
+++ b/docs/en/latest/deployments/gke.md
@@ -66,6 +66,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/k3s-rke.md
b/docs/en/latest/deployments/k3s-rke.md
index c87c59e6..94618ae6 100644
--- a/docs/en/latest/deployments/k3s-rke.md
+++ b/docs/en/latest/deployments/k3s-rke.md
@@ -67,6 +67,22 @@ If you are using K3s, the default kube config file is
located in `/etc/rancher/k
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/kind.md
b/docs/en/latest/deployments/kind.md
index d8a5342f..dedaea35 100644
--- a/docs/en/latest/deployments/kind.md
+++ b/docs/en/latest/deployments/kind.md
@@ -70,6 +70,22 @@ helm install apisix apisix/apisix \
kubectl get service --namespace ingress-apisix
```
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/kubesphere.md
b/docs/en/latest/deployments/kubesphere.md
index 2f77c802..82001819 100644
--- a/docs/en/latest/deployments/kubesphere.md
+++ b/docs/en/latest/deployments/kubesphere.md
@@ -65,6 +65,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/minikube.md
b/docs/en/latest/deployments/minikube.md
index 6394d85c..06cfc93e 100644
--- a/docs/en/latest/deployments/minikube.md
+++ b/docs/en/latest/deployments/minikube.md
@@ -54,6 +54,22 @@ helm install apisix apisix/apisix \
kubectl get service --namespace ingress-apisix
```
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
diff --git a/docs/en/latest/deployments/tke.md
b/docs/en/latest/deployments/tke.md
index 7e60c7c2..428bf5b8 100644
--- a/docs/en/latest/deployments/tke.md
+++ b/docs/en/latest/deployments/tke.md
@@ -72,6 +72,22 @@ Else, if your Kubernetes cluster version is under `v1.16`,
set the flag `--set i
:::
+:::tip
+
+APISIX Ingress also supports (beta) the new [Kubernetes Gateway
API](https://gateway-api.sigs.k8s.io/).
+
+If the Gateway API CRDs are not installed in your cluster by default, you can
install it by running:
+
+```shell
+kubectl apply -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.5.0/standard-install.yaml
+```
+
+You should also enable APISIX Ingress controller to work with the Gateway API.
You can do this by adding the flag `--set
ingress-controller.config.kubernetes.enableGatewayAPI=true` while installing
through Helm.
+
+See [this
tutorial](https://apisix.apache.org/docs/ingress-controller/tutorials/configure-ingress-with-gateway-api)
for more info.
+
+:::
+
This will create the five resources mentioned below:
* `apisix-gateway`: dataplane the process the traffic.
