avi-helm-charts

AKO: Avi Kubernetes Operator

Run AKO

AKO runs as a POD inside the Kubernetes cluster.

Pre-requisites

To Run AKO you need the following pre-requisites:

• Step 1: Configure an Avi Controller with a vCenter cloud. The Avi Controller should be versioned 18.2.10 / 20.1.2 or later.
• Step 2:
  • Make sure a PG network is part of the NS IPAM configured in the vCenter
• Step 3: If your POD CIDRs are not routable: Data path flow is as described below: The markers in the drawing are described below:
  1. The client requests a specified hostname/path.
  2. The DNS VS returns an IP address corresponding to the hostname.
  3. The request is forwarded to the resolved IP address that corresponds to a Virtual IP hosted on an Avi Service Engine. The destination IP in the packet is set as the POD IP address on which the application runs.
  4. Service Engines use the static route information to reach the POD IP via the next-hop address of the host on which the pod is running.
  5. The pod responds and the request is sent back to the client.
     • Create a Service Engine Group dedicated to a Kubernetes cluster.
• Step 3.1: If your POD CIDRs are routable then you can skip step 2. Ensure that you skip static route syncing in this case using the disableStaticRouteSync flag in the values.yaml of your helm chart.
• Step 4: Kubernetes 1.16+.
• Step 5: helm cli pointing to your kubernetes cluster.

Note: We only support helm 3

Install using helm

For instructions on installing AKO using helm please use this link

AKO CRDs

Read more about AKO CRDs

AKO in Openshift Cluster

AKO can be used in openshift cluster to configure Routes and Services of type Loadbalancer. For details about how to use AKO in an openshift cluster and features specific to openshift refer here.

Using NodePort mode

Service of type NodePort can be used to send traffic to the pods exposed through Service of type NodePort.

This feature supports Ingress/Route attached to Service of type NodePort. Service of type LoadBalancer is also supported, since kubernetes populates NodePort by default. AKO will function either in NodePort mode or in ClusterIP mode.

A new parameter serviceType has been introduced as config option in AKO’s values.yaml. To use this feature, set the value of the parameter to NodePort.

Parameter	Description	Default
configs.serviceType	Type of Service to be used as backend for Routes/Ingresses	ClusterIP
nodeSelectorLabels.key	Key used as a label based selection for the nodes in NodePort mode.	empty
nodeSelectorLabels.value	Value used as a label based selection for the nodes in NodePort mode.	empty

Kubernetes populates NodePort by default for service of type LoadBalancer. If config.serviceType is set to NodePort, AKO would use NodePort as backend for service of type Loadbalancer instead of using Endpoints, which is the default behaviour with config.serviceType set as ClusterIP.

AKO in Public Clouds

Please refer to this page for details on support for ClusterIP mode for GCP and Azure IaaS cloud in Avi Controller.

Tenancy in AKO

Please refer to this page for support in AKO to map each kubernetes / OpenShift cluster uniquely to a tenant in Avi.

Networking/v1 Ingress Support

Please refer to this page for details on how AKO supports and implements networking/v1 Ingress and IngressClass.

AKO objects

Please refer to this page for details on how AKO interprets the Kubernetes objects and translates them to Avi objects.

FAQ

For some frequently asked question refer here