You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A self-signed cert in a well known secrets store would be fantastic with an option to go non-SSL only during deployment for those who don't need or want SSL would be a welcome addition.
Another option could be to not use a public IP at all and use the port proxy, leaving the decision to export it to a public IP up to the implementer.
At least on GKE, the idea you may want to ingress into K8S from the inside network seems to not have been dreamt up yet unless I've severely misread the docs (which is quite possible!), making SSL fairly mandatory when using the LoadBalancer stanza on GKE.
The text was updated successfully, but these errors were encountered:
davisein
pushed a commit
to davisein/elastickube
that referenced
this issue
Apr 11, 2016
A self-signed cert in a well known secrets store would be fantastic with an option to go non-SSL only during deployment for those who don't need or want SSL would be a welcome addition.
Another option could be to not use a public IP at all and use the port proxy, leaving the decision to export it to a public IP up to the implementer.
At least on GKE, the idea you may want to ingress into K8S from the inside network seems to not have been dreamt up yet unless I've severely misread the docs (which is quite possible!), making SSL fairly mandatory when using the LoadBalancer stanza on GKE.
The text was updated successfully, but these errors were encountered: