CRW upgrade fails 2.5 to 2.6 in proxied environment

Hello,

Customers upgrading CRW from 2.5 to 2.6 in a proxied environment are facing issues with the CRW pod coming up, given that the workaround as mentioned in CRW-1565 is applied.

Later after investigation it came to our notice that for the parameter `nonProxyHosts: .svc` to take effect, it was also necessary the parameter `useInternalClusterSVCNames: true` is present.

But even before discovering this, the customer did manage to get the stack up by adding the below parameters

customCheProperties:
 JAVA_OPTS: -Djavax.net.ssl.trustStore=/home/user/cacerts -Djavax.net.ssl.trustStorePassword=changeit

However, it is expected that the upgrade sets this parameter(useInternalClusterSVCNames) by default as it seems to have been introduced in 2.6 and so there were issues when the JAVA truststore opts were also not added.

Customer quote:

~~~
Yes, setting useInternalClusterSVCNames: true allows the components to communicate without the javastore JAVA settings in place. It looks like this option was introduced in 2.6 to allow the components to communicate with their internal service names. Our upgrade didn't set this parameter & so there were issues when the JAVA truststore opts were also not added manually or via the upgrade.

We will now use useInternalClusterSVCNames: true instead of the additional JAVA settings.
~~~

Regards,

Anirudh Gudi