Migration guide for upgrading from 3.x to 4.0

[s-geiger-si]

Objective: write a README section documenting the migration steps from chart v3 to v4

---

Original post:

What happened?

Flux tried to automatically upgrade from 3.4.1 to 4.0.0 and this leads to the following error:

Helm upgrade failed for release <namespace>/jaeger with chart jaeger@4.0.0: cannot patch "jaeger-agent" with kind Service: Service "jaeger-agent" is invalid: spec.clusterIPs[0]: Invalid value: []string{"None"}: may not change once set && cannot patch "jaeger-collector" with kind Service: Service "jaeger-collector" is invalid: spec.clusterIPs[0]: Invalid value: []string{"None"}: may not change once set && cannot patch "jaeger-query" with kind Service: Service "jaeger-query" is invalid: spec.clusterIPs[0]: Invalid value: []string{"None"}: may not change once set

Am I expected to uninstall and redeploy jaeger or is there a migration path? If so, is this documented anywhere?

Steps to reproduce

1. Deploy jaeger 3.4.1
2. Deploy jaeger 4.0.0 via upgrade (i.e., using flux)

Expected behavior

Upgrade works automatically, or migration guidelines define what needs to be prepared pre-upgrade.

Relevant log output

Screenshot

No response

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

[yurishkuro]

if you are using chart v3.x you are still running jaeger-v1, which is EOL this month. I think you do need to uninstall it (sorry I am not an expert in Helm). I would recommend trying chart v4 on a test cluster first to ensure your setup is working.

[s-geiger-si]

Thanks for the quick response. I was kind-of hoping for that the chart team had some migration notes, something like this:

https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.4-Release-Notes#upgrading-from-spring-boot-33 (but for the jaeger helm chart)

I guess the issue is that the all-in-one chart is now the default but in v1 the separate deployments were used.

[yurishkuro]

all I can do is tag this help-wanted. If you end up performing / confirming upgrade steps please post here.