Add details for how to properly create the route_tls_secret kubernetes secret object

[michaelford85]

For the installation of Automation Controller, the documentation specifies that for an Openshift route, you can add the parameter route_tls_secret. However, no details are provided on the parameter names for the secret itself. This is what ended up working for me:

kubectl create secret generic tls_creds --from-file=tls.crt=client.pem --from-file=tls.key=client-key.pem --from-file=ca.crt=ca.pem

Adding these details to the documentation would make things more clear when trying to support TLS encryption.

[muyari]

@michaelford85 I cant figure out how to get this part working in OpenShift. When i look at secrets after the deployment of AWX there are a bunch of random secrets. The ones of note seem to be the one with 4 secret values ca.crt, namespace, service-ca.crt and token.

Not sure how to go about implementing these and in which order... I tried adding them when creating the route via the console but errors :( any tips would be awesome!!