I tried your steps on a 1.4.7 clusters and it was WAI. What does kubectl
describe ingress show you? How did you create your secret? I assume you did
something like:
```
$ openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /tmp/tls.key
-out /tmp/tls.crt -subj
Thanks for the suggestion (great tutorial!).
But even after changing the secret type and recreating both the ssl & the
ingress objects - I still do not see that the service is exposed externally
(and no LB is created in GCE).
$ kubectl get svc|grep 8080
echoheaders10.99.243.152
Try setting the secret type to `kubernetes.io/tls` ?
You can see examples of real running services at
https://github.com/kubernetes/k8s.io/tree/master/reviewable.k8s.io
On Wed, Dec 21, 2016 at 11:54 AM, Paul Podolny wrote:
> I have uploaded the SSL key & cert as a
I have uploaded the SSL key & cert as a 'secret' and made my ingress use it.
However, after creating an ingress rule for my service for I don't see any
associated external IP and no LB was created in GCE:
$ kubectl run echoheaders
--image=gcr.io/google_containers/echoserver:1.3 --port=8080
$
Ingress objects represent Google Cloud Load Balancer instances, whcih
can handle SSL termination *and* act as load-balancers.
On Tue, Dec 20, 2016 at 2:17 PM, wrote:
> Hi Folks,
>
> A noob question -
>
> What is the recommended way to expose an app via LB with SSL