Affects Version/s: Casablanca Release
Fix Version/s: Casablanca Release
AAF services are using locator for linking clients with aaf-service.
If AAF service is in Kubernetes then locator store its' internal port which is valid only inside Kubernetes. If call to locator is made from outside of kubernetes:
Then response is with internal port:
The port is from internal port range, not from external, so any CADI client can not connect to aaf-service due to inaccessible port number outside of kubernetes