@cmoulliard Is there any specific use-case for which we need this Nodeport? The existing ClusterIP service works fine, right?

The existing ClusterIP service works fine, right?

Yes, it works fine but it is mainly used for internal usage when pod access gitea internally using the kube service address OR when the service should be managed behind an ingress host

Is there any specific use-case for which we need this Nodeport?

As mentioned this is to allow a pod to access gitea from another kind cluster.

cluster 1 : kind cluster running gitea = gitea.cnoe.localtest.me:8443
cluster 2 : kind cluster where a pod (aka a git client) will access gitea running on the cluster 1. In this case, the pod will resolve the address: gitea.cnoe.localtest.me to localhost/127.0.0.01 and will not be able to access: gitea.cnoe.localtest.me:8443