GSLB Service Is Not Created Because OpenShift Route Is Missing VS UUID/Controller UUID Annotations
search cancel

GSLB Service Is Not Created Because OpenShift Route Is Missing VS UUID/Controller UUID Annotations

book

Article ID: 444789

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

  • The GSLB Service is not created for the configured OpenShift Route.
  • The Route is not updated with the required VS UUID, Controller UUID annotations, and status information after AKO synchronization.
  • The screenshot below shows the Route without the required VS UUID/Controller UUID annotations and an empty status (status: {}).
  • The screenshot below shows an example of a Route with the expected annotations and populated status.

Environment

OpenShift Cluster where AKO/AMKO Running
AKO: 2.1.3
AMKO: 2.1.1

VMware Avi Load Balancer

Cause

  • When AKO is configured in Dedicated SNI mode, it skips updating the OpenShift Route with the required VS UUID, Controller UUID annotations, and status if the Route is configured with insecureEdgeTerminationPolicy: Allow. As a result, AMKO skips processing the Route, and the GSLB Service is not created.
  • To verify the AKO deployment mode (Dedicated VS mode), run:
    kubectl get configmap avi-k8s-config -n avi-system -o yaml 
    shardVSSize: DEDICATED
  • AKO log:
    kubectl logs -n avi-system <ako-pod-name> 
    status/route_status.go:47 Skipping update of parent VS annotation since the route : <route-name> has InsecureEdgeTerminationAllow set to true 
  • AMKO log
    kubectl logs -n avi-system <amko-pod-name> 
    msg: skipping route because either VS UUID or controller UUID missing from annotations

Resolution

Workaround:

Configure AKO to use Shared VS mode by changing shardVSSize from DEDICATED to SMALL, MEDIUM, or LARGE.

  1.  Edit the AKO ConfigMap:
    kubectl edit configmap avi-k8s-config -n avi-system
  2. Update the shardVSSize value. 
    shardVSSize: SMALL
  3. Save the changes and restart the AKO pod:
    kubectl delete pod -n avi-system <ako-pod-name>
  4.  Redeploy the OpenShift Route so that AKO reprocesses it and updates the required annotations. Once the Route is updated, verify that the GSLB Service is created successfully.

Fix Version:

The fix for this issue is planned to be included in a future AKO release 2.3.1.