Currently the tls-termination within the kubernetes-setup is done by the ingress. This is bad, because traffic between the ingress and hanami-pod is unencrypted and these 2 don't have to run on the same node. There is another container within the hanami-pod required, with does the tls-termination order to fix this security issue.
Acceptance Criteria
the ingress only forward the encrypted traffic without termination of the tls-encryption
an new container is created within the hanami-pod, which terminates the tls-connection
QA
Description
Currently the tls-termination within the kubernetes-setup is done by the ingress. This is bad, because traffic between the ingress and hanami-pod is unencrypted and these 2 don't have to run on the same node. There is another container within the hanami-pod required, with does the tls-termination order to fix this security issue.
Acceptance Criteria
Blocked by
How to test