<p>Im not sure if im doing something wrong here, maybe you guys can help me out.</p>

<p>I have 2 net core APIs in a kubernetes cluster in the same namespace - according to documentation I should be able to hit the API using service discovery - this is the route im hitting <code>http://sourceapi-service.dev.svc.cluster.local</code> with a get. The naming is correct of the service and the namespace.</p>

<p>When I check the logs I see that the API does receive the request but 404s while trying to find a controller action that matches the request.</p>

<pre><code>[15:05:02 INF] Request starting HTTP/1.1 GET http://sourceapi- 
service.dev.svc.cluster.local//api/Customer/HOLI15
[15:05:02 DBG] Wildcard detected, all requests with hosts will be allowed.
[15:05:02 DBG] No candidates found for the request path '//api/Customer/HOLI15'
[15:05:02 DBG] Request did not match any endpoints
[15:05:02 DBG] The request path  does not match the path filter
[15:05:02 DBG] Connection id "0HLRC72O1EQ8J" completed keep alive response.
[15:05:02 INF] Request finished in 51.0505ms 404
</code></pre>

<p>When I make the request via my ingress it works just fine.</p>

<p>What am I doing wrong ? Is there some sort of proxy rules  that I need to setup?</p>

cl0ud
<p>Well this is embarrassing. </p>

<p>The double / in the route broke it . I changed  <code>//api/Customer/HOLI15</code> to <code>/api/Customer/HOLI15</code> and it worked.</p>

<p>Nothing to see here.</p>
