Avi Kubernetes Operator
Overview
The Avi Vantage platform integration with OpenShift/Kubernetes provides a redesigned architecture involving a new operator called Avi Kubernetes Operator (AKO). The following illustration outlines the components of the Avi Kubernetes integration.
Avi Kubernetes Operator (AKO)
AKO is an operator which works as an ingress controller and performs Avi-specific functions in an OpenShift/Kubernetes environment with the Avi Controller. It runs as a pod in the cluster and translates the required OpenShift/Kubernetes objects to Avi objects and automates the implementation of ingresses/routes/services on the Service Engines (SE) via the Avi Controller.
The Avi Controller
The Avi Controller provides the central control, management, and observability functions in the Avi architecture. It manages the lifecycle of the Service Engines, their configurations, and provides centralized analytics and observability.
The Avi Service Engines (cluster-external)
The Avi Service Engines are the data-plane engines that implement the virtual services for Kubernetes ingresses. These SEs handle all the data plane responsibilities in the platform.
The following table provides a comprehensive list of documentation for the Avi OpenShift/Kubernetes integration using AKO:
| CRDs References |
|---|
| Setting up Routing Rules using CRDs |
| Avi Infra Setting CRD |
| Use Case: Public Cloud References |
|---|
| AKO in GCP |
| AKO in Azure |
| AKO Deployment in GKE, AKS, and EKS |
| Use Case: Tanzu References |
|---|
| AKO on TKGs with NSX-T |
| Use Case: Other References |
|---|
| AKO in OpenStack |
| AKO on Istio |
| Shared VIP |
| Passthrough Ingress |
| Multiple AKO Instances in a Cluster |
| Other References |
|---|
| Default Secret for TLS Routes |
| Default Secret for TLS Ingresses |
| Namespace Sync in AKO |
| Kubernetes Events |
| FAQ and Troubleshooting References |
|---|
| Frequently Asked Questions |
| Troubleshooting Guide |