-
Type:
Suggestion
-
Resolution: Fixed
-
None
-
Affects Version/s: None
-
Component/s: Environment - Kubernetes
-
None
The Confluence Helm Chart documents:
confluence:
ports:
# -- The port on which the Confluence container listens for HTTP traffic
#
http: 8090
However, changing the above value to a custom value such as Port 8093 only affects the Readiness Probe port check which ultimately fails.
% kubectl describe pod confluencelocal-0 Name: confluencelocal-0 Namespace: confluence ... .. IP: 10.1.1.38 ... .. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 9m19s default-scheduler Successfully assigned confluence/confluencelocal-0 to docker-desktop Normal Pulled 9m18s kubelet Container image "alpine" already present on machine Normal Created 9m18s kubelet Created container nfs-permission-fixer Normal Started 9m18s kubelet Started container nfs-permission-fixer Normal Pulled 9m17s kubelet Container image "atlassian/confluence:7.13.5" already present on machine Normal Created 9m17s kubelet Created container confluence Normal Started 9m17s kubelet Started container confluence Warning Unhealthy 4m14s (x59 over 9m4s) kubelet Readiness probe failed: Get "http://10.1.1.38:8093/status": dial tcp 10.1.1.38:8093: connect: connection refused
The cause of this is that the Helm Chart does not actually change Confluence Tomcat to listen on the custom port.
Suggestion:
Update the Helm Chart deployment to automatically set the ATL_TOMCAT_PORT environment variable to the value in confluence.ports.http from the Helm chart values.
Workaround:
To update the Confluence/Tomcat to a custom port value, also set the ATL_TOMCAT_PORT environment variable in the Helm Chart values file. e.g.
confluence:
ports:
http: 8093
additionalEnvironmentVariables:
- name: ATL_TOMCAT_PORT
value: "8093"