<p>I'm using Kubernetes with Traefik as Ingress Controller. I've some web services within my network that can't be containerized yet. Therefore I'm looking for a way to expose my non-Kubernetes web services through the Traefik Ingress. I've no more public IP's, so splitting both environments is not an option.</p>

<p>I've made an endpoint + service to solve this issue, but when I try to connect I get an SSL Protocol Error. Am I doing something wrong or does someone have another solution?</p>

<p>These are my (test)endpoints and service yaml:</p>

<pre><code>kind: Endpoints
apiVersion: v1
metadata:
  name: my-service
subsets:
  - addresses:
      - ip: 10.4.0.6
    ports:
      - port: 443
---
kind: Service
apiVersion: v1
metadata:
  name: my-service
spec:
  ports:
  - protocol: TCP
    port: 443
    name: https
    targetPort: 443
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  annotations:
    kubernetes.io/ingress.class: traefik
spec:
  rules:
  - host: host.com
    http:
      paths:
      - path: /*
        backend:
          serviceName: my-service
          servicePort: 443
</code></pre>

Ferron Nijland
<p>For starters, I bet that when you <code>kubectl describe svc my-service</code> you have empty endpoints, even though endpoints do exist, right ?</p>

<p>To fix that, you need to adapt your endpoints <code>ports</code> key to have the same ports definition as your service has (name, protocol etc.). You should then see these endpoints in <code>describe service</code> results and be able to use it normally.</p>
