CNG: gitlab-workhorse port can be configured in the charts but changes are not reflected in the containers
Summary
The unicorn
chart's values.yaml
, allows us to modify the workhorseInternalPort
, which is then reflected in the Kubernetes manifests, but not in the actual application.
It seem that the actual port the process bind to is hardcoded, baked in the registry.gitlab.com/gitlab-org/build/cng/gitlab-workhorse-*
image itself and can't be easily override atm: see here.
Steps to reproduce
- deploy brand new release from upstream with following settings:
helm template --set certmanager-issuer.email=jdoe@inter.net --set gitlab.unicorn.service.workhorseInternalPort=8005 . | kubectl apply -f -
Current behavior
The stack comes up, but the workhorse
is listening on port 8181
instead of the port set in gitlab.unicorn.service.workhorseInternalPort
.
Expected behavior
Ideally, workhorse
config should reflect the change we made in the charts. If not, in worst case, user should not be able to modify that value in the chart.
Versions
- Chart:
1.9.3
- Platform: Self-hosted with bootkube
- Kubernetes:
- Client:
v1.13.3
- Server:
v1.12.9
- Client:
- Helm: (
helm version
)- Client:
v2.9.1
- Server: N/A
- Client:
Edited by Hossein Pursultani