Even with ECK 2.4, I'm still able to reproduce this error. Fleet Server invalid argument "tcp://10.233.110.49:8220" for "--fleet-server-port". I did find that it only appears to happen when I create a service with the same name as the agent. So in this case the agent name is fleet-server and the Service of type Load Balancer is also named fleet-server. If I don't have the load balancer or use a different name, everything works just fine. Thoughts??
I figured it out. Its because K8S automatically injects ENV vars of services and since I have a service named fleet-server it creates an env var called FLEET_SERVER_PORT which is an actual var from fleet server and causes the conflict.
1 Like
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.