Avi Kubernetes Operator Guide 1.13

AKO 1.13 1.12 1.11 1.10

Troubleshooting for GatewayAPI

AKO
 supports Gateway API v1beta1 (under tech preview). This section provides a list of troubleshooting guidelines for this feature.

Gateway is created but the parent virtual service is not created on
AKO

  • Ensure
    featuregate
     for Gateway is enabled in values.yaml and that the
    ako-gateway
     container is running in the AKO pod
  • Check the status of Gateway, if Gateway has any invalid spec.
  • See Gateway API for details on required fields for gateway objects.
  • Check if Gateway class is attached to Gateway and the Controller on Gateway class is set to AKO
    ako.vmware.com/avi-lb
    . By default, a Gateway class named avi-lb should already be created.
  • Parent VS name is of the form ako-gw-(clustername)--(namespace)-(gatewayName)-EVH

Gateway class was created after Gateway creation

AKO
 does not check for gateways if gateway class was created after gateway creation. To resolve this, do one of the following:
  • Update/re-create the gateway object
  • Restart
    AKO

Gateway class is deleted but VS objects are not deleted

Deleting gateway class does not delete VS objects. This is to mitigate deletion of multiple objects due to accidental deletion of gateway class. To delete Parent VS, delete the corresponding gateway object.
To trigger delete with gateway class deletion, restart
AKO
 after gateway deletion.

HTTPRoute is created but child VS is not created on
AKO

  • Check pod event if HTTPRoute was found to be invalid.
  • Matches and BackendRefs required fields for Child VS creation.
  • See Gateway API for details on required fields for gateway objects
  • Check if the parent VS is created and the status of corresponding gateway for any possible errors.

Content feedback and comments