<p>I have a k3s cluster running and I have the last 12 hours trying to figure out why I cannot get a response from a simple nginx pod...</p>
<p>I have metalLB setup in BGP with pfsense using FRR this is the BGP output:</p>
<pre><code>BGP table version is 1, local router ID is 192.168.2.1, vrf id 0
Default local pref 100, local AS 64501
Status codes:  s suppressed, d damped, h history, * valid, &gt; best, = multipath,
               i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, &lt; announce-nh-self
Origin codes:  i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*= 192.168.10.1/32  192.168.4.103                          0 64500 ?
*&gt;                  192.168.4.101                          0 64500 ?

Displayed  1 routes and 2 total paths
</code></pre>
<p>192.168.4.101-103 are my nodes.</p>
<p>Current svc output:</p>
<p><a href="https://i.stack.imgur.com/CQNjt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CQNjt.png" alt="enter image description here" /></a></p>
<p>Pods:</p>
<p><a href="https://i.stack.imgur.com/ysn0X.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ysn0X.png" alt="enter image description here" /></a></p>
<p>I am stumped where to start looking...</p>
<p>curl 192.168.10.2 gives a timeout</p>
<p>traceroute gives no route to host</p>
<p>NGINX was simply deployed as so:</p>
<pre><code>kubectl create deployment nginx --image k8s.gcr.io/nginx:latest
kubectl expose deployment nginx --type=LoadBalancer --port=80
</code></pre>

ck3mp
<p>I'm guessing you don't have a BGP route that can forward any traffic to your <code>nginx</code> service. Perhaps you can modify your BGP route from <code>192.168.10.1/32</code> to <code>192.168.10.0/24</code>, which is the <code>LoadBalancer</code> IP subnet that your services are using inside the cluster. You've currently fixed this to just a single IP address that none of your services in the cluster are using and every incoming packet is being dropped.</p>
<p>If that doesn't work, you might have to change your service type to 'NodePort' which will bind your service endpoint to the NodeIP on which the pod is running. This will allow you to use NodeIPs to connect to your service (which is what you appear to be doing in your current BGP setting).</p>
