AMKO: Avi Multi Kubernetes Operator

What's AMKO?

AMKO provides application load-balancing across multiple kubernetes clusters using AVI's enterprise grade GSLB capabilities.

GSLB - Load balancing across instances of the application that have been deployed to multiple locations (typically, multiple data centers and/or public clouds). Avi uses the Domain Name System (DNS) for providing the optimal destination information to the user clients.

AMKO is aware of the following object types:

• Kubernetes

  • Ingress
  • Service type load balancer

• Openshift

  • Routes
  • Service type load balancer

Dependencies

Pre-requisites

To kick-start AMKO, we need:

1. Atleast one kubernetes/openshift cluster.

2. Atleast one AVI controller.

3. AMKO assumes that it has connectivity to all the member clusters' kubernetes API servers. Without this, AMKO won't be able to watch over the kubernetes and openshift resources in the member clusters.

4. Before deploying AMKO, one of the clusters have to be designated as the leader and rest of the clusters as followers. AMKO has to be deployed on all clusters (wherever federation is required). This is to ensure that the leader cluster's AMKO would federate the AMKO config objects like GSLBConfig and GlobalDeploymentPolicy objects to all follower clusters. See this for more details on the specifics of federation and how to recover from a disaster recovery scenario.

5. On all clusters, create a namespace avi-system:

   $ kubectl create ns avi-system

6. Create a kubeconfig file with the permissions to read the service and the ingress/route objects for all the member clusters. Follow this tutorial to create a kubeconfig file with multi-cluster access. Name this file gslb-members and generate a secret with the kubeconfig file in cluster-amko by following:

   $ kubectl create secret generic gslb-config-secret --from-file gslb-members -n avi-system

   This has to be done for all the member clusters wherever AMKO is going to be deployed.

Note that the permissions provided in the kubeconfig file for all the clusters must have atleast the permissions to [get, list, watch] on:

• Kubernetes ingress and service type load balancers.
• Openshift routes and service type load balancers. AMKO also needs permissisons to [create, get, list, watch, update, delete] on:
• GSLBConfig object
• GlobalDeploymentPolicy object

Install using helm

Note that only helm v3 is supported.

Following steps have to be executed on all member clusters:

1. Create the avi-system namespace:

   $ kubectl create ns avi-system

Note: Helm version 3.8 and above will be required to proceed with helm installation.

2. Search the available charts for AMKO:

   $ helm show chart oci://projects.registry.vmware.com/ako/helm-charts/amko --version 1.13.1
   
   Pulled: projects.registry.vmware.com/ako/helm-charts/amko:1.13.1
   Digest: sha256:xyxyxxyxyx
   apiVersion: v2
   appVersion: 1.13.1
   description: A helm chart for Avi Kubernetes Operator
   name: amko
   type: application
   version: 1.13.1

3. Use the values.yaml from this repository to provide values related to Avi configuration. To get the values.yaml for a release, run the following command

   helm show values oci://projects.registry.vmware.com/ako/helm-charts/amko --version 1.13.1 > values.yaml
   

   Values and their corresponding index can be found here

4. To configure federation via values.yaml:

   • Set configs.federation.currentClusterIsLeader to true for the leader cluster. For all follower clusters, set this to false.
   • Set configs.federation.currentCluster to the current cluster context.
   • Add the member clusters to configs.federation.memberClusters.

5. Install AMKO:

   $ helm install --generate-name oci://projects.registry.vmware.com/ako/helm-charts/amko --version 1.13.1 -f /path/to/values.yaml  --set configs.gsllbLeaderController=<leader_controller_ip> --namespace=avi-system

6. Check the installation:

   $ helm list -n avi-system
   
   NAME             NAMESPACE   REVISION    UPDATED                                 STATUS      CHART                   APP VERSION
   amko-1598451370  avi-system  1           2023-10-14 11:16:21.889538175 +0000 UTC deployed    amko-1.13.1             1.13.1

Troubleshooting and Log collection

If you face any issues during installing/configuring/using AMKO, see if your problem is listed in the troubleshooting page.

Follow this to gather logs for tech-support in case of an unrecoverable failure.

Uninstall using helm

helm uninstall -n avi-system <amko-release-name>

If a user needs to remove the already created GSLB services, one has to remove the GDP object first. This will remove all the GSLB services selected via the GDP object.

kubectl delete gdp -n avi-system global-gdp

Typically, an AMKO instance could have been deployed in the avi-system namespace. But, if it is not, then the avi-system namespace can also be removed:

kubectl delete ns avi-system

Upgrade AMKO using helm

Follow these steps if you are upgrading from an older AMKO release.

Step1

Update the helm repo with the following command:

helm repo update amko

Step2

Helm does not upgrade the CRDs during a release upgrade. Before you upgrade a release, run the following command to download and upgrade the CRDs:

helm template oci://projects.registry.vmware.com/ako/helm-charts/amko --version 1.13.1 --include-crds --output-dir <output_dir>

This will save the helm files to an output directory which will contain the CRDs corresponding to the AMKO version. To install the CRDs:

kubectl apply -f <output_dir>/amko/crds/

Step3

helm list -n avi-system

NAME            NAMESPACE   REVISION    UPDATED                                     STATUS      CHART       APP VERSION
amko-1598451370 avi-system  1           2023-06-19 10:00:31.609195757 +0000 UTC     deployed    amko-1.10.1 1.10.1

Step4

Get the values.yaml for the AMKO version 1.13.1 and edit the values as per the requirement.

helm show values oci://projects.registry.vmware.com/ako/helm-charts/amko --version 1.13.1 > values.yaml

Step5

Upgrade the helm chart

helm upgrade amko-1598451370 oci://projects.registry.vmware.com/ako/helm-charts/amko -f /path/to/values.yaml --version 1.13.1 --set configs.gslbLeaderController=<IP or Hostname> --set gslbLeaderCredentials.password=<username> --set gslbLeaderCredentials.username=<username> --namespace=avi-system

parameters

Custom resources

AMKO uses a custom resource to configure federation to member clusters:

• AMKOCluster

AMKO uses the following custom resources to configure the GSLB services in the GSLB leader site:

1. GSLBConfig
2. GlobalDeploymentPolicy

Follow the above links to take a look at the CRD objects and how to use them.

If AMKO is installed via helm, it by default creates one instance of each type in the avi-system namespace. To see these objects:

$ kubectl get amkocluster amkocluster-federation -n avi-system
NAME                       AGE
amkocluster-federation     45m

$ kubectl get gc -n avi-system gc-1
NAME            AGE
gc-1            45m

$ kubectl get gdp -n avi-system
NAME         AGE
global-gdp   46m

Note that, only one instance of each GDP and GSLBConfig is supported and AMKO will ignore other instances.

3. GSLBHostRule: Override specific GslbService properties. No instances are created by default (helm install). Users have to create these in the avi-system namespace. To see these objects:

   $ kubectl get gslbhostrule -n avi-system

Editing runtime parameters of AMKO

The GDP object can be edited at runtime to change the application selection parameters, traffic split and the applicable clusters. AMKO will recognize these changes and will update the GSLBServices accordingly.

Changing only logLevel is permissible at runtime via an edit of the GSLBConfig. For all other changes to the GSLBConfig, the AMKO pod has to be restarted.

Choosing a mode of GslbService FQDN

There can be different requirements for a user to either use local FQDNs as the GslbService FQDNs, or use a different FQDN as the Global FQDN. Please see this to choose a mode fit for the use-case and enable accordingly.

Gslb Service Properties

Certain Gslb Service properties can be set and modified at runtime. If these are set through the GDP object, they are applied to all the Gslb Services. If a user wants to override specific properties, they can use a GSLBHostRule object for a GslbService.

To set them, follow steps for GlobalDeploymentPolicy and for GSLBHostRule.