-
Type:
Suggestion
-
Resolution: Fixed
-
None
-
Affects Version/s: None
-
Component/s: Environment - Kubernetes
-
None
The Confluence Helm Chart documents:
synchrony:
ports:
# -- The port on which the Synchrony container listens for HTTP traffic
#
http: 8091
However, changing the above value to a custom value such as Port 8099 only affects the Readiness Probe port check which ultimately fails.
% kubectl describe pod confluencelocal-synchrony-0 Name: confluencelocal-synchrony-0 Namespace: confluence ... IP: 10.1.1.39 ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 10m default-scheduler Successfully assigned confluence/confluencelocal-synchrony-0 to docker-desktop Normal Pulled 10m kubelet Container image "atlassian/confluence:7.13.5" already present on machine Normal Created 10m kubelet Created container synchrony Normal Started 10m kubelet Started container synchrony Warning Unhealthy 33s (x597 over 10m) kubelet Readiness probe failed: Get "http://10.1.1.39:8099/heartbeat": dial tcp 10.1.1.39:8099: connect: connection refused
The cause of this is that the Helm Chart does not actually change Synchrony to listen on the custom port.
Suggestion:
Update the Helm Chart deployment to automatically set the -Dsynchrony.port JVM Flag to the value in synchrony.ports.http from the Helm chart values.
Workaround:
To update Synchrony to a custom port value, also set the -Dsynchrony.port JVM flag in the Helm Chart values file. e.g.
synchrony:
ports:
http: 8099
additionalJvmArgs:
- -Dsynchrony.port=8099