<p>I have an issue on which am blocked since few days . Tried lot of things but none worked .</p>

<p>I have a k8s cluster in which I have a pod running corda (<a href="https://docs.corda.net/docker-image.html" rel="nofollow noreferrer">https://docs.corda.net/docker-image.html</a>) . This pod expose a RPC endpoint (10201), endpoint that I want to be able to reach from outside the cluster (my laptop) using the corda-shell tool .</p>

<p>So I created an ingress (using ingress-nginx) and added a config-map that looks like that :</p>

<pre><code>apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ .Release.Name }}-tcp-services
  namespace: {{ .Release.Namespace }}
data:
  10201: {{ .Release.Namespace }}/{{ .Release.Name }}-corda-node:10201
</code></pre>

<p>The service.yaml for the corda pod looks like this :</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: {{ include "corda-node.fullname" . }}
  labels:
{{ include "corda-node.labels" . | indent 4 }}
spec:
  type: ClusterIP
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http
    - port: 10200
      targetPort: p2p
      protocol: TCP
      name: p2p
    - port: 10201
      targetPort: rpc
      protocol: TCP
      name: rpc
    - port: 10202
      targetPort: rpcadmin
      protocol: TCP
      name: rpcadmin
  selector:
    app.kubernetes.io/name: {{ include "corda-node.name" . }}
    app.kubernetes.io/instance: {{ .Release.Name }}
</code></pre>

<p>But so far, no matter what I tried I was not able to connect to it from the outside .
From another pod / container in the cluster it is working fine, same as when I'm port-forwarding to my local .</p>

<p>Note : I can connect to other services in my cluster from the outside . In fact this corda pod has a sidecar which expose an API on 8080 and I can access it .</p>

<p>I can see the port '10201' being exposed by the ingress, so I guess it took my tcp-services into account, but does not seem to be able to forward the request to the corda pod .</p>

<p>If I try to do <code>telnet public-ip-of-the-cluter 10201</code> , I just have a timeout .
Same when running the <code>corda-shell</code> tool ...</p>

<p>I see no relevant logs in the ingress-controller pod as far as I can tell .</p>

<p>I created a <a href="https://github.com/tbrunain/k8s-connectivity-issues" rel="nofollow noreferrer">small github repo</a> with various 'kubectl describe xxx' commands in order to give you an overview of what I did .</p>

<p>If you need more info just ask me . Am really struggling with that, most likely I'm doing something stupid somewhere ... </p>

<p>Thanks !</p>

<p>EDIT :</p>

<p>I put the logs of the ingress on - --v=3 , I can see this when it starts :</p>

<blockquote>
  <p>I0215 09:30:32.081819       6 controller.go:333] Searching Endpoints
  with TCP port number 10201 for Service
  "salmon-locust/salmon-locust-corda-node-corda-node"<br>
  │ │ I0215 09:30:32.081836       6 endpoints.go:74] Getting Endpoints
  for Service "salmon-locust/salmon-locust-corda-node-corda-node" and
  port &amp;ServicePort{Name:rpc,Protocol:TCP,Port:10201,TargetPort:{1 0
  rpc},NodePort:0,}                  │ │ I0215 09:30:32.081849       6
  endpoints.go:117] Endpoints found for Service
  "salmon-locust/salmon-locust-corda-node-corda-node": [{10.96.1.13
  10201
  &amp;ObjectReference{Kind:Pod,Namespace:salmon-locust,Name:salmon-locust-corda-node-corda-
  │</p>
</blockquote>

<p>But no activity when I’m trying to connect to it via the corda-tools-shell.</p>

<p>EDIT 2 :</p>

<p>We found what was the issue, the ingress -> dns resolved to the cloudflare proxy, which was not handling the 1xxxx port ...</p>

nothingtoseehere
<p>We found what was the issue, the ingress -> dns resolved to the cloudflare proxy, which was not handling the 1xxxx port ...</p>
