Add missing secretName for Ingress

[Hijbk304]

Add missing secretName on create Ingress. For #2254

[openshift-ci]

Hi @Hijbk304. Thanks for your PR.

I'm waiting for a infinispan member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Crumby]

@Hijbk304 @ryanemerson I don't think the solution here will be as simple as adding the secretName to the Ingress specs. According Ingress TLS documenationt it requires for the secret to have data in tls.crt and tls.key format. And while we support that we also support keystore.p12 format which wouldn't work.

The second and probably more important issue is that Ingress with TLS terminates the encryption and forwards plain text but the server is still configured for the encrypted communication. I suspect the PR as is doesn't work but I didn't get a chance to test it and we run the tests with NodePort configuration in the CI/CD only.