<p>Kubernetes surfaces an API proxy, which allows querying the internal services via eg:  <a href="https://myhost.com/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard/" rel="nofollow noreferrer">https://myhost.com/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard/</a></p>

<p>This is all well, and good. However, for security &amp; compliance reasons, all of our services expose an HTTPS endpoint. Attempting to access them by going to <a href="https://myhost/api/v1/proxy/namespaces/default/services/myhttpsservice:3000/" rel="nofollow noreferrer">https://myhost/api/v1/proxy/namespaces/default/services/myhttpsservice:3000/</a>   results in</p>

<pre><code> Error: 'read tcp 172.20.122.129:48830-&gt;100.96.29.113:3000: read: connection reset by peer' 
Trying to reach: 'http://100.96.29.113:3000/'
</code></pre>

<p>Because the endpoint, 100.96.29.113:3000 is in fact https. </p>

<p>Is there any way to configure the proxy to apply SSL to specific service endpoints?</p>

<p>(Edit: If this is not currently possible, a relevant github issue link for tracking the feature request is also acceptable answer until it will be)</p>

<p>As documented at <a href="https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls</a>, (and pointed out on slack), you can access services behind HTTPS by prefixing the servicename with "https:"  ; </p>

<p>Using the example from above, correctly it would be: <a href="https://myhost/api/v1/proxy/namespaces/default/services/https:myhttpsservice:3000/" rel="nofollow noreferrer">https://myhost/api/v1/proxy/namespaces/default/services/https:myhttpsservice:3000/</a></p>
