An Ingress publishes HTTP services under host names and paths. It is only a set of rules; an ingress controller, chosen with ingressClassName, does the routing. Each rule names a host and a list of paths, and each path sends traffic to a Service by name and port. The port is the Service's, never the container's.
pathType decides what matches. Prefix matches the path and everything under it, segment by segment, so /reports covers /reports/daily but /report does not. Exact matches one path only. When several paths match, the longest wins, whatever their order.
TLS takes a tls entry listing the hosts and a kubernetes.io/tls Secret in the same namespace. The controller terminates TLS and forwards plain HTTP, so the application doesn't change. Requests that match no rule get the controller's default backend, usually a 404.
One host, every path, over TLS.