AMKO: GSLB Pool member and public IP was removed once ingress is recreated.
search cancel

AMKO: GSLB Pool member and public IP was removed once ingress is recreated.

book

Article ID: 383184

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

AMKO: GSLB Pool member and public IP was removed once ingress is recreated.

Resolution

GSLB pool is not added because PUT Request failed with below error:

2024-11-05T07:25:00.718Z     [33mWARN [0m    utils/avi_rest_utils.go:135    RestOp method PUT path /api/gslbservice/gslbservice-xxxxx
---snip---

can't handle error code 400: map[error:All Gslb pool members should have the same type of configuration - all or none should have public IP.], won't retry

On addition of ingress when existing GSLBService is present AMKO was not able to identify PublicIP from GSLBHostRule.

 

Workaround:

==========

Workaround is to do an update on GSLBHostrule or re-create GSLBHostrule . That should populate the publicIP correctly.

 

Updating the existing GSLBHostrule

>Edit the Yaml file
>Update any parameter and apply the settings.
>kubectl apply -f <gslbhostrule.yaml> -n <namespace>

 

Recreating the GSLBHostrule
>kubectl delete -f <gslbhostrule.yaml> -n <namespace>
>kubectl apply -f <gslbhostrule.yaml> -n <namespace>

 

Resolution:

=========

Issue will be fixed via AMKO 1.13.1 version

Additional Information