Istio

The following document will take you through the process of installing, verifying the installation, and uninstalling Gloo Portal for Istio.

Prerequisites

For this guide, we’ll need the following:

• helm (version v3.0.0 or higher)
• kubectl
• A compatible Kubernetes cluster setup (1.16 or higher), to which you can connect via kubectl
• Istio 1.5 or higher installed to your cluster
• An Istio Gateway that will expose your APIs

Note on Istio Gateways

Gloo Portal will configure Istio to expose your APIs on one or more Gateways. When installing, you can configure which Gateways should be targeted via dedicated values in the Gloo Portal Helm chart.

By default, these values are:

istio:
  gateways:
  - name: istio-system/istio-ingressgateway
    ports:
    - port: 80
      targetPort: 8080
    - port: 443
      targetPort: 8443

• name identifies a Gateway resource and must be in the <gateway namespace>/<gateway name> format.
• ports is an optional attribute; it represents a set of mappings between the port which is exposed on the gateway service and the one on which the actual gateway proxy workloads listen on. Starting with Istio 1.6 (see here), these ports can be different. If the ports are the same, then the attribute can be omitted; else users need to specify mappings for the relevant Gateway ports.

For example, the default values would work if the following resources are in place:

apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  labels:
    release: istio
  name: istio-ingressgateway
  namespace: istio-system
spec:
  selector:
    app: istio-ingressgateway
    istio: ingressgateway
  servers:
  - hosts:
    - '*'
    port:
      name: http
      number: 80
      protocol: HTTP

---

# This is the Kubernetes service that exposes the above Gateway
apiVersion: v1
kind: Service
metadata:
  name: istio-ingressgateway
  namespace: istio-system
spec:
  clusterIP: 10.20.12.129
  externalTrafficPolicy: Cluster
  # Other ports omitted for brevity
  ports:
  - name: http2
    port: 80
    protocol: TCP
    targetPort: 8080
  - name: https
    port: 443
    protocol: TCP
    targetPort: 8443
  selector:
    app: istio-ingressgateway
    istio: ingressgateway
  type: LoadBalancer

Installation

To install Gloo Portal you’ll use a Helm chart. You will also need a license key to submit as part of the chart deployment. If you do not have a license key, you can request one by clicking on “Get a Demo” on our website.

First we will add the repository with the Helm chart and update the repo contents.

# Add the Helm repository for Gloo Portal
helm repo add gloo-portal https://storage.googleapis.com/dev-portal-helm
helm repo update

Then we will create the target namespace for the deployment and install Gloo Portal. Replace the LICENSE_KEY placeholder with your license key.

# Create the namespace and install the Helm chart
kubectl create namespace gloo-portal
helm install gloo-portal gloo-portal/gloo-portal -n gloo-portal --set licenseKey.value=LICENSE_HERE --set istio.enabled=true

Helm will create an installation named gloo-portal.

NAME: gloo-portal
LAST DEPLOYED: XXXXXXXXXXX
NAMESPACE: gloo-portal
STATUS: deployed
REVISION: 1
TEST SUITE: None

Verify your Installation

To verify that your installation was successful, check that the Gloo Portal deployments and services have been created. If you choose to install into a namespace other than gloo-portal, you will need to query your chosen namespace instead.

kubectl get all -n gloo-portal

NAME                                            READY   STATUS             RESTARTS   AGE
pod/ext-auth-service-847c77dff6-ldt56           1/1     Running            0          5m
pod/gloo-portal-admin-server-676c656bd8-tcwkm   3/3     Running            0          5m
pod/gloo-portal-controller-f646b5f4b-hb7dd      1/1     Running            0          5m
pod/rate-limiter-f5d95bf8b-tshf2                1/1     Running            0          5m
pod/redis-799fc7c785-dgfrn                      1/1     Running            0          5m

NAME                               TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
service/ext-auth-service           ClusterIP   10.105.196.67            8083/TCP,9091/TCP,8082/TCP   5m
service/gloo-portal                ClusterIP   10.104.251.104           8080/TCP                     5m
service/gloo-portal-admin-server   ClusterIP   10.105.199.172           8080/TCP                     5m
service/rate-limiter               ClusterIP   10.104.204.151           8083/TCP,8084/TCP,9091/TCP   5m
service/redis                      ClusterIP   10.110.89.127            6379/TCP                     5m

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ext-auth-service           1/1     1            1           5m
deployment.apps/gloo-portal-admin-server   1/1     1            1           5m
deployment.apps/gloo-portal-controller     1/1     1            1           5m
deployment.apps/rate-limiter               1/1     1            1           5m
deployment.apps/redis                      1/1     1            1           5m

NAME                                                  DESIRED   CURRENT   READY   AGE
replicaset.apps/ext-auth-service-847c77dff6           1         1         1       5m
replicaset.apps/gloo-portal-admin-server-676c656bd8   1         1         1       5m
replicaset.apps/gloo-portal-controller-f646b5f4b      1         1         1       5m
replicaset.apps/rate-limiter-f5d95bf8b                1         1         1       5m
replicaset.apps/redis-799fc7c785                      1         1         1       5m

Please refer to the Architecture page for more details about what function each deployment serves.

Uninstall

To uninstall Gloo Portal simply run the following command:

helm uninstall gloo-portal -n gloo-portal

Next Steps

After installing the product, you may want to walk through the Concepts and Getting Started guides.