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
manageTLS mounts the certificates onto the runtime pods, but the runtime is responsible for loading the mounted certificates. Liberty containers load the certificates automatically into the default keystore / truststore at container startup. tWAS runtime doesn't have such equivalence. Document that the inorder for manageTLS to work end-to-end, runtime must load the certs.
Document this in the limitation / troubleshooting section
The text was updated successfully, but these errors were encountered:
The current workaround to install tWAS applications using RCO v1.2.0 is to use spec.route.termination: edge with insecureEdgeTerminationPolicy: Redirect or insecureEdgeTerminationPolicy: Allow or spec.route.termination: passthrough
manageTLS mounts the certificates onto the runtime pods, but the runtime is responsible for loading the mounted certificates. Liberty containers load the certificates automatically into the default keystore / truststore at container startup. tWAS runtime doesn't have such equivalence. Document that the inorder for manageTLS to work end-to-end, runtime must load the certs.
Document this in the limitation / troubleshooting section
The text was updated successfully, but these errors were encountered: