yivan-atl

@Ansible-man you must be be doing it wrong. I have just tested it and it works for me: ``` helm install confluence ./ \ --set ingress.create=true \ --set ingress.host=hello.com \...

@inka the snippet you shared should override both proxy name in `server.xml` and synchrony url for you. Though your ingress.host does not look right. Do you expect **Confluence** to be...

@inka what you are saying is that when you set ATL_PROXY_NAME in additional env vars in Helm values to confluence.my.url.com it is still synchrony-confluence.my.url.com as set in ingress.host? Please note...

Fixed by https://github.com/atlassian/data-center-helm-charts/pull/822

@BryanGuffeySonos indeed, there have been a few cases involving app tunnels. We'll definitely take a look at it, thanks for raising it!

Released in 1.22.5. Docs: https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#tunnels

Same issue with `awsclustercontrolleridentities.infrastructure.cluster.x-k8s.io`, operator is complaining about caBundle but it is complaining about `spec.conversion.webhookClientConfig.caBundle`, not `spec.conversion.webhook.clientConfig.caBundle` as it is in the actual CRD.

@nagarajuvemula789 you can set in your values: ``` jira: additionalJvmArgs: - -Dhttp.proxyHost=proxy.example.org - -Dhttp.proxyPort=8080 - -Dhttps.proxyHost=proxy.example.org - -Dhttps.proxyPort=8080 - -Dhttp.nonProxyHosts=localhost ```

@nagarajuvemula789 I disagree that a new Helm values stanza is more intuitive than passing jvm args. We can't make own section for every possible configuration, that's why there are additionalJvmArgs...

@iancward thanks for the heads up. Must be 1.18(and no bugfix version) that caused it. This will be fixed.