Before reporting an issue

• I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

operator

Describe the bug

I tried to migrate my image to the latest (25.0.0), then I installed the newest k8s operator.

But the pods would always be marked as unhealthy, and I could never reach the admin console.

The errors I got were these:

 Startup probe failed: Get "http://10.244.197.15:9000/health/started": d │
│ ial tcp 10.244.197.15:9000: connect: connection refused                                                                              │
│   Warning  Unhealthy  80s (x12 over 91s)  kubelet            Startup probe failed: Get "http://10.244.197.15:9000/health/started": E │
│ OF

I don't know if this was enough to prevent access, but FWIW, I simply couldn't access the console or the clients.

After trying a few times, I tried to build an image with the hostname:v1 feature enabled. It didn't help.

I don't see a particular fail on the logs.

I had to rollback to an older operator and to 24.0.5.

Version

25.0.0

Regression

• The issue is a regression

Expected behavior

I expected to be able to access the console and to log in.

Actual behavior

Pods don't report as healthy. Console inaccessible.

How to Reproduce?

I installed the new operator, and built a newer image.

Anything else?

No response