<p>I have a working Nexus 3 pod, reachable on port 30080 (with NodePort): <a href="http://nexus.mydomain:30080/" rel="nofollow noreferrer">http://nexus.mydomain:30080/</a> works perfectly from all hosts (from the cluster or outside).</p>
<p>Now I'm trying to make it accessible at the port 80 (for obvious reasons).</p>
<p>Following the docs, I've implemented it like that (trivial):</p>
<pre><code>[...]
---

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: nexus-ingress
  namespace: nexus-ns
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: nexus.mydomain
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: nexus-service
              servicePort: 80
</code></pre>
<p>Applying it works without errors. But when I try to reach <a href="http://nexus.mydomain" rel="nofollow noreferrer">http://nexus.mydomain</a>, I get:</p>
<blockquote>
<p>Service Unavailable</p>
</blockquote>
<p>No logs are shown (the webapp is not hit).</p>
<p>What did I miss ?</p>

spi
<p><a href="https://www.civo.com/blog/k8s-vs-k3s#:%7E:text=K3s%20is%20a%20fully%20CNCF,apply%20against%20a%20k3s%20cluster." rel="nofollow noreferrer">K3s Lightweight Kubernetes</a></p>
<blockquote>
<p>K3s is designed to be a single binary of less than 40MB that completely implements the Kubernetes API. In order to achieve this, they removed a lot of extra drivers that didn't need to be part of the core and are easily replaced with add-ons.</p>
</blockquote>
<p>As I mentioned in comments, K3s as default is using <a href="https://doc.traefik.io/traefik/" rel="nofollow noreferrer">Traefik</a> <code>Ingress Controller</code>.</p>
<blockquote>
<p>Traefik is an open-source Edge Router that makes publishing your services a fun and easy experience. It receives requests on behalf of your system and finds out which components are responsible for handling them.</p>
</blockquote>
<p>This information can be found in <a href="https://rancher.com/docs/k3s/latest/en/networking/" rel="nofollow noreferrer">K3s Rancher Documentation</a>.</p>
<blockquote>
<p>Traefik is deployed by default when starting the server... To prevent <code>k3s</code> from using or overwriting the modified version, deploy <code>k3s</code> with <code>--no-deploy traefik</code> and store the modified copy in the <code>k3s/server/manifests</code> directory. For more information, refer to the official Traefik for Helm Configuration Parameters.</p>
<p>To disable it, start each server with the <code>--disable traefik</code> option.</p>
</blockquote>
<p>If you want to deploy <a href="https://kubernetes.github.io/ingress-nginx/" rel="nofollow noreferrer">Nginx Ingress controller</a>, you can check guide <a href="https://dev.to/sr229/how-to-use-nginx-ingress-controller-in-k3s-2ck2" rel="nofollow noreferrer">How to use NGINX ingress controller in K3s</a>.</p>
<p>As you are using specific <code>Nginx Ingress</code> like <code>nginx.ingress.kubernetes.io/rewrite-target: /$1</code>, you have to use <code>Nginx Ingress</code>.</p>
<p>If you would use more than 2 <code>Ingress controllers</code> you will need to force using <code>nginx ingress</code> by <code>annotation</code>.</p>
<pre><code>  annotations:
    kubernetes.io/ingress.class: &quot;nginx&quot;
</code></pre>
<p>If mention information won't help, please provide more details like your <code>Deployment</code>, <code>Service</code>.</p>
