To correct this you can have the Zone CP rebuild this configmap. You will need to first delete the original configmap using the following command on the Zone CP:
kubectl delete configmap <configmapname> -n <namespace>
Afterwards, redeploy the Zone CP and the configmap will be rebuilt. For example, if helm was used to deploy:
helm upgrade -n kong-mesh-system --values values.yaml kong-mesh kong-mesh/kong-mesh
We recommend validating that the license itself is correct on both the Global CP and the Zone CP after the deployment. To validate that you can run the following command:
kubectl get configmap license-quota-status -o yaml -n <namespace>
The output should be identical when run on the Global and Zone CP. Once the configmap is rebuilt the issue should be resolved.
If this occurs on Universal, please verify if you are running on Memory or backed by a database.
If this occurs while running on Memory please deploy out a database to resolve this issue. Memory data storage is intended for demo purposes.
Each Zone CP is intended to be backed by a database in universal.