This message was deleted.

Not sure if it can help, running

kubectl describe svc --namespace default mytomcat

returns:

Name:                     mytomcat
Namespace:                default
Labels:                   app.kubernetes.io/instance=mytomcat
                          app.kubernetes.io/managed-by=Helm
                          app.kubernetes.io/name=tomcat
                          app.kubernetes.io/version=10.1.18
                          helm.sh/chart=tomcat-10.13.4
Annotations:              meta.helm.sh/release-name: mytomcat
                          meta.helm.sh/release-namespace: default
Selector:                 app.kubernetes.io/instance=mytomcat,app.kubernetes.io/name=tomcat
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       10.43.156.225
IPs:                      10.43.156.225
Port:                     http  80/TCP
TargetPort:               http/TCP
NodePort:                 http  32078/TCP
Endpoints:                10.42.0.10:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type    Reason                Age   From                Message
  ----    ------                ----  ----                -------
  Normal  EnsuringLoadBalancer  24m   service-controller  Ensuring load balancer
  Normal  AppliedDaemonSet      24m                       Applied LoadBalancer DaemonSet kube-system/svclb-mytomcat-8afa4a31

you can set nodeport and type nodeport so you can easily test the deployment. I'm not sure how rancher desktop handles service type loadbalancer... (that's the default for this helm chart)

thanks a lot Pedro!

or if already installed

I think the problem was that I had port 80 in use, changing

service.ports.http

also worked (the external ip got assigned, and I could access the service)

ah nice

now I am experimenting with nodeport 🙂

if it got an external ip (and valid) then I would just keep testing with that