Hello Bert,
thank you for your reply.
When we encrypt the openshift route, we see the valid certification.
Actually we did have the service configured as LoadBalancer. I’ve changed it to ClusterIP but the result is the same.
Your idea of using a ConfigMap is good, we will take a look at it, after we get the server running.
The curl command shows the following:
* About to connect() to staging-axon.intern.company.de port 443 (#0)
* Trying 172.xx.xx.xx...
* Connected to staging-axon.intern.company (172.xx.xx.xx) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: E=hostmaster@company.de,CN=staging-axon.intern.company,OU=Openshift Operations,O=COMPANY,L=XX,ST=XX,C=XX
* start date: Mar 12 10:46:53 2021 GMT
* expire date: Mar 12 10:46:53 2023 GMT
* common name: staging-axon.intern.company
* issuer: CN=company Issuing CA,DC=intern,DC=company,DC=de
> GET /actuator/info HTTP/1.1
> User-Agent: curl/7.29.0
> Host: staging-axon.intern.company.de
> Accept: */*
>
< HTTP/1.1 400
< Content-Type: text/plain;charset=ISO-8859-1
< Connection: close
< Set-Cookie: e848677014042990746df48xxx=77da5bdf2xx; path=/; HttpOnly; Secure
<
Bad Request
This combination of host and port requires TLS.
* Closing connection 0
We are going to look at the problem now from the OpenShift side - we think the problem might be as you expected the service.
Thank you very much for your caring, Bert.
Kind regards,
Alexander
Edit: Because I am new I cant post more than 2 links - so please see the URL as it is, ended with .de