Accessing remote tracking server since move to http based transport server

[schauaib]

Hi,

I used to deploy a aim (3.17.5) tracking server in a kubernetes pod, and I was able to expose this server thanks to a k8s service.
Then, I was able to reach out the server from another pod (with same version of aim package installed) using following command (for instance):
aim runs --repo aim://<serviceName>.<namespace>.svc.cluster.local:<service port> ls

However, I recently upgraded my server to v3.21.0 (which is based on http transport layer instead of grpc one as far as I understood), and now I am facing an error when executing the exact same command from the client side (of course I also upgraded the client package to 3.21.0): "RuntimeError: Failed to connect to Aim Server. Have you forgot to run aim server command?"

Should I change anything in the way I start the server up or in the way the client tries to reach it out ?

Thanks for your help

[schauaib]

After additional investigation, the issue only occurs when starting the aim tracking server with SSL options. Is I run "aim server" without key&certificate, I am able to reach it out properly...