Open ParadoxGuitarist opened 5 years ago
@ParadoxGuitarist Are you referring to a particular stack that does not support HTTPS?
Certificates should be stored as secrets in the cluster, e.g. oc create secret tls tls-secret --cert=path/to/tls.cert --key=path/to/tls.key
. Then, the deployment configuration could be set-up to use this secret. Does AppsodyApplication
custom resource support the consumption of such secrets?
Is your feature request related to a problem? Please describe. Currently only http is supported on the stacks. Most cloud deployments would be able to proxy that connection from the container to elsewhere, but it may be possible in all deployments. It would be nice to be able to encrypt coming out of the container if so desired.
Describe the solution you'd like If configured via yaml or ENV (?) the docker image copies over server.key and public.key files from specified location (or project root?) into the docker image. If no keys are present, self signed keys are generated. The exposed port uses https instead of http.
Describe alternatives you've considered You can use a proxy, or ingress to encrypt traffic, but I would think that adding configuration from appsody for any of those would be complicated.