<p>I have questions about my basic understanding about the setup of my k8s cluster.</p>
<p>I have a K8s running on Hetzner-cloud and allocated a &quot;physical&quot; <code>Loadbalancer</code> (which can be controlled via <code>annotations</code> on a Service.)
I use a nginx (or traefik) as my <code>ingress-controller</code>.</p>
<p>Please correct me if I am wrong:</p>
<ol>
<li>I create the service <code>Loadbalancer</code> with the <code>annotations</code> in the same <code>namespace</code> of my <code>ingress-controller</code> right?</li>
<li>Then I create an <code>ingress</code> with label <code>kubernetes.io/ingress-controller=nginx</code> in my <code>default</code> namespace with the settings to point to my services in the <code>default</code> namespace (one for frontend, one for backend)</li>
</ol>
<p><strong>Is this the correct way to set this up?</strong></p>

Jan
<p>1.- No. Ingress Controller and your workload doesn't have to be in the same namespace. In fact, you will have the Ingress Controller running in a separate namespace than your workload.</p>
<p>2.-Yes. Generally speaking your <code>Ingress</code> rules, meaning your <code>Ingress</code> object, meaning your <code>Ingress</code> yaml and your <code>Service</code> must be in the same namespace. So <code>Ingress</code> can't transpass a namespace.</p>
<p><strong>Note: There is a way to have an <code>Ingress</code> object to send trafffic to a <code>Service</code> in a different namespace.</strong></p>
