https on minikube is broken

Describe the bug Bad https endpoint, SSL error on fresh install of AES 1.0.0 on Minikube. Verbose curl results in:

curl -v https://192.168.64.5:30845
* Rebuilt URL to: https://192.168.64.5:30845/
*   Trying 192.168.64.5...
* TCP_NODELAY set
* Connected to 192.168.64.5 (192.168.64.5) port 30845 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number
* stopped the pause stream!
* Closing connection 0
curl: (35) error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number

To Reproduce

1. Steps to reproduce the behavior:
2. Fresh minikube install
3. Install latest AES 1.0 (1/17/20) from docs using the 4-line install script
4. Verify you can reach the Ambassador splashscreen at http://192.168.64.3:32534/
5. Click the link on the page for console (url of link: https://192.168.64.5:30845/edge_stack/admin)
6. See ERR_SSL_PROTOCOL_ERROR in Chrome.

Expected behavior https endpoint presents a warning page in Chrome that allows you to ignore the cert issue as per the docs.

Versions (please complete the following information):

• Image: quay.io/datawire/aes:1.0.0
• Image ID: docker-pullable://quay.io/datawire/aes@sha256:4a6577ca83178fbbfd8295d68312b2d92b6820dfd97e6a36e2ec1337ac4cf66b
• minikube version: v1.6.2

Additional context Add any other context about the problem here.

[alechp]

Is this what others are seeing?

[jimmya]

@alechp yes. I ran into exactly the same issue when running ambassador through minikube.