Connection refused after upgrade to 17

Problem to solve

Describe your question in as much detail as possible:

There are 2 pipelines that begin fail after upgrade to version 17, I’m receiving error 'connection refused during deploy:


I already created the variables KUBE_CONTEXT and KUBE_INGRES_BASE_DOMAIN, environment, etc.

Steps to reproduce

Add variable AUTO_DEVOPS_DEPLOY_DEBUG = true, but I don´t know to do furthet

Configuration

production:
image: “registry.gitlab.com/gitlab-org/cluster-integration/cluster-applications:v2.3.0
stage: production
environment:
name: production
script:
- helm repo add ingress-nginx Welcome - Ingress-Nginx Controller
- |
if [[ “kubectl get --all-namespaces ingress -o name | wc -l” != “0” ]]
then
helm upgrade --reuse-values ingress-nginx ingress-nginx/ingress-nginx
else
helm upgrade --install nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --set rbac.create=true --set controller.publishService.enabled=true --set controller.admissionWebhooks.enabled=false --set controller.service.loadBalancerIP=XX.XX.XXX.XXX --create-namespace
fi

Versions

Please select whether options apply, and add the version information.

  • Self-managed
  • [ x ] GitLab.com SaaS
  • Self-hosted Runners

We are having issues with Pipeline after 17 upgrade. The error you are reporting I think is called out in A guide to the high-impact breaking changes in GitLab 17.0 and we resolved by Migrating to the new runner registration workflow | GitLab

The problem I’m stuck on is Pipelines are not being created after repo updates since the upgrade.