very nice, thanks!

(just to understand where are the ingress rules)

kubectl get ingress -A

That’s very helpful, thanks!. BTW when I enter that command I get No resources found in clearml namespace. Similarly if I run:
kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services clearml
I get:
Error from server (NotFound): services "clearml" not found I

and add these 3 hostnames pointing them to the external ip

s o kubectl -n clearml get ingress

you need 3 records

sounds good I’ll give that a shot real quick

If you have ALB you will just need to add some annotations on ingress rules depending on your setup. btw for now , since you already have everything in place, I suggest to just add values to /etc/hosts and see if it works

I’m happy to use AWS’s ALB I was just even less sure about how to set that up at the time. I assume I need to setup a Target Group Attachement to the clearml-webserver ip address, correct?

Hi BeefyHippopotamus73 , on EKS it’s preferrable to use ALB but you can also work with your nginx. You need DNS records with hostnames you setup pointing to that External IP. If you just need to test, you can simply add entries in you client machine /etc/hosts file (if you are on *nix)

JuicyFox94