*test-connection pod always fails on Helm

[samueljsmalmeida]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe the bug

Both kratos/oathkeeper-test-connection pods fail avertime.
As every k8s resource is deployed at the same time, and the test pods are a simple busybox running a 1 time wget, the test pods are ready well before the rest of the stack.
A simple solution for this would be to add a sleep before the wget, or even expose the test command on the helm values.

Reproducing the bug

helm repo add ory https://k8s.ory.sh/helm/charts
helm install my-oathkeeper ory/oathkeeper --version 0.59.0

And/or

helm repo add ory https://k8s.ory.sh/helm/charts
helm install my-kratos ory/kratos --version 0.59.0

Relevant log output

Relevant configuration

Version

Chart 0.59.0 / App v0.40.9

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

No response

[Demonsthere]

The test-connection pods are only deployed/used when you are running helm test which assumes that a release was already installed. Please see https://helm.sh/docs/topics/chart_tests/

[samueljsmalmeida]

The test-connection pods are only deployed/used when you are running helm test which assumes that a release was already installed. Please see https://helm.sh/docs/topics/chart_tests/

I'm afraid that's incorrect, if you follow the steps to replicate the bug on a new installation, you'll see the test pods running and failing.

[Demonsthere]

This has to be environment related (version of helm/k8s/kubectl), on my machine and the CI the behavior is as expected:

❯ make k3d-run
...
❯ helm ls -A
NAME       	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART                        	APP VERSION
postgresql 	default    	1       	2026-01-19 09:27:16.982862 +0100 CET   	deployed	postgresql-18.2.0            	18.1.0
prometheus 	default    	1       	2026-01-19 09:27:47.404395 +0100 CET   	deployed	kube-prometheus-stack-81.0.0 	v0.88.0
traefik    	kube-system	1       	2026-01-19 08:27:09.133448008 +0000 UTC	deployed	traefik-27.0.201+up27.0.2    	v2.11.10
traefik-crd	kube-system	1       	2026-01-19 08:27:08.608544091 +0000 UTC	deployed	traefik-crd-27.0.201+up27.0.2	v2.11.10
❯ helm repo add ory https://k8s.ory.sh/helm/charts
"ory" already exists with the same configuration, skipping
❯ kubectx
k3d-ory-k8s
❯ helm install my-oathkeeper ory/oathkeeper --version 0.59.0
NAME: my-oathkeeper
LAST DEPLOYED: Mon Jan 19 09:28:30 2026
NAMESPACE: default
STATUS: deployed
REVISION: 1
DESCRIPTION: Install complete
❯ kubectl get pods -A
NAMESPACE     NAME                                                   READY   STATUS      RESTARTS   AGE
default       my-oathkeeper-565c88f764-vbdps                         0/1     Running     0          9s
default       postgresql-0                                           1/1     Running     0          82s
default       prometheus-grafana-84b795c78-nqgbf                     3/3     Running     0          45s
default       prometheus-prometheus-node-exporter-45l55              1/1     Running     0          45s
kube-system   coredns-ff8999cc5-wcqv5                                1/1     Running     0          99s
kube-system   helm-install-traefik-crd-ln582                         0/1     Completed   0          100s
kube-system   helm-install-traefik-hvx5j                             0/1     Completed   1          100s
kube-system   local-path-provisioner-698b58967b-7grpp                1/1     Running     0          99s
kube-system   metrics-server-8584b5786c-qsx9t                        1/1     Running     0          99s
kube-system   svclb-traefik-6c6eeca4-j44kn                           2/2     Running     0          90s
kube-system   traefik-5c57d75bc9-2qglg                               1/1     Running     0          90s
prometheus    prometheus-kube-prometheus-operator-64696fddf6-cwjpc   1/1     Running     0          45s
prometheus    prometheus-prometheus-kube-prometheus-prometheus-0     2/2     Running     0          42s

Please compare your environment with the one used in the repo, this might be a change of behavior in helm v4 that I am unaware of