tokers commented on a change in pull request #180: URL: https://github.com/apache/apisix-ingress-controller/pull/180#discussion_r560689039
########## File path: docs/deployments/gke.md ########## @@ -0,0 +1,76 @@ +<!-- +# +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# +--> + +# Install Ingress APISIX on Google Cloud GKE + +This document explains how to install Ingress APISIX on [Google Cloud GKE](https://cloud.google.com/kubernetes-engine). + +## Prerequisites + +* Create an Kubernetes Service on GKE. +* Install [Google Cloud SDK](https://cloud.google.com/sdk) and get the credentials or you can just use the [Cloud Shell](https://cloud.google.com/shell). +* Install [Helm](https://helm.sh/). +* Clone [Apache APISIX Charts](https://github.com/apache/apisix-helm-chart). +* Clone [apisix-ingress-controller](https://github.com/apache/apisix-ingress-controller). +* Make sure your target namespace exists, kubectl operations thorough this document will be executed in namespace `ingress-apisix`. + +## Install APISIX + +[Apache APISIX](http://apisix.apache.org/) as the proxy plane of apisix-ingress-controller, should be deployed in advance. + +```shell +cd /path/to/apisix-helm-chart +helm repo add bitnami https://charts.bitnami.com/bitnami +helm dependency update ./chart/apisix +helm install apisix ./chart/apisix \ + --set gateway.type=LoadBalancer \ + --set allow.ipList="{0.0.0.0/0}" \ + --namespace ingress-apisix +kubectl get service --namespace ingress-apisix +``` + +Two Service resources were created, one is `apisix-gateway`, which processes the real traffic; another is `apisix-admin`, which acts as the control plane to process all the configuration changes. + +The gateway service type is set to `LoadBalancer`, so that clients can access Apache APISIX through the [GKE Load Balancer](https://cloud.google.com/kubernetes-engine/docs/concepts/service#services_of_type_loadbalancer) . You can find the load balancer IP by running: + +```shell +kubectl get service apisix-gateway --namespace ingress-apisix -o jsonpath='{.status.loadBalancer.ingress[].ip}' +``` + +Another thing should be concerned that the `allow.ipList` field should be customized according to the [Pod CIRD configuration of GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr), so that the apisix-ingress-controller instances can access the APISIX instances (resources pushing). + +## Install apisix-ingress-controller + +You can also install apisix-ingress-controller by Helm Charts, it's recommended to install it in the same namespace with Apache APISIX. + +```shell +cd /path/to/apisix-ingress-controller +# install base resources, e.g. ServiceAccount. +helm install ingress-apisix-base -n ingress-apisix ./charts/base +# install apisix-ingress-controller +helm install ingress-apisix ./charts/ingress-apisix \ + --set ingressController.image.tag=dev \ + --set ingressController.config.apisix.baseURL=http://apisix-admin:9180/apisix/admin \ + --set ingressController.config.apisix.adminKey=edd1c9f034335f136f87ad84b625c8f1 \ + --namespace ingress-apisix +``` + +Change the `ingressController.image.tag` to the Apache APISIX version that you desire. You have to Wait for while until the correspdoning pods are running. Review comment: Fixed. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
