[ https://issues.jboss.org/browse/TEIIDSB-92?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-92: --------------------------------------- [~rareddy] here is what this looks like: https://github.com/shawkins/teiid-openshift-examples/commit/3dba649fcbd57... Before this is merged it would need to be targeted against the security example instead. The basic idea is that we need a new svc.yml to define a secure transport. It has to include the service.alpha.openshift.io/serving-cert-secret-name annotation. Then in the deploymentconfig there is an initContainer to take the generated certificate and turn it into a keystore, a volume to share it, and additional env properties to enable the secure transport and provide the keystore. This requires a later version of f-m-p - and it requires that the container name be spring-boot. If it's named something else, them f-m-p creates an extra invalid container in the generated deployment. I'll log something with f-m-p just so it's captured. A minor complication with this approach (or with having a single Teiid ssl config) is when you have both services as secure - you end up with a single key/keystore as they both are given the same name. It doesn't really matter which one, but if you care about what is presented as the host name it would be good to know. -- This message was sent by Atlassian Jira (v7.12.1#712002)