Configures HELM_UPGRADE_EXTRA_ARGS to --values my-values.yaml
with
ingress:
enabled: false
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
It dosent seem to disable ingress as I can still access from public URL any idea what I am a doing wrong,
tkuah
January 6, 2020, 10:16am
2
Based on https://gitlab.com/gitlab-org/charts/auto-deploy-app/blob/master/templates/ingress.yaml , I think you would need to disable service
instead. So:
service:
enabled: false
BTW, from GitLab 12.6 onwards, you can use .gitlab/auto-deploy-values.yaml
file instead of using HELM_UPGRADE_EXTRA_ARGS
. See https://docs.gitlab.com/ee/topics/autodevops/#build-and-deployment
2 Likes
@tkuah Yes I tried
service:
enabled: false
With no luck I am using 2.5.5, it still pushes it to the ingress and assigns dns
tkuah
January 7, 2020, 8:28am
4
@robertom
With no luck I am using 2.5.5, it still pushes it to the ingress and assigns dns
With service.enabled
set to false
, there should be no Ingress
resource rendered by helm. Is that the case ? You should be able to verify this with kubectl get ingress -n <your project namespace>
.
BTW What project/software does 2.5.5 refer to ?
tkuah
January 7, 2020, 11:06am
6
Ah the whitespace is significant (it’s YAML), so you need:
service:
enabled: false
Yes I have it correct with no luck
I was able to get it working by adding the Environment to .gitlab-ci.yml instead of using the HELM_UPGRADE_EXTRA_ARGS variables file.
.gitlab-ci.yml
production:
variables:
HELM_UPGRADE_EXTRA_ARGS: --set service.enabled=false --set ingress.enable=false
1 Like