Thanks,
I spent a couple days more and got a better understanding. Sorry about
confusing the OS with the JVM memory settings.
I was able to get a much happier container by using the newest, newest openjdk
image:
redhat-openjdk-18/openjdk18-openshift
This image uses the -XX:+UnlockExperiment
Most likely redeploying the master certificates is all that needs to be
done from the start but I haven't verified this myself. That value really
only affects the additional names that the master certificates are signed
for.
On Fri, Jun 15, 2018 at 11:26 AM, Thomas Hikade
wrote:
> .. and then yo
.. and then you will also need to run "redeploy master certificates", else
you will get SSL handshake errors on subsequent playbook runs, due to the
new name not being part of the master certificate's SAN names.
https://docs.openshift.org/latest/install_config/redeploying_certificates.html#redeplo
Hi Wolf,
Given the silence, we've decided to go with the RPM method, as it's the
default for Centos/non-Atomic.
Thanks,
Joel
On Thu, Jun 14, 2018 at 3:21 PM Wolf Noble wrote:
> I’ve been in the process of trying to assess this myself.
>
> Interested to hear what you settle on regardless
>
>
>