Istio 1.4.0 tracing service moved from port 80 to 9411 #19227
Comments
|
Associated commit appears to be 9e0887f#diff-264788198be8f0b9371c31fecce6d199 and issue #17204 |
|
Nodeport more trouble then it is worth... These two PRs need a revert. The author is free to resubmit the work. |
|
Had a deeper look at the PR. With @Stono for the moment, I am going to make a small surgical change that should exhibit the original behavior. |
Fixes: istio#19227 The tracing and zipkin services both point to the same workload with the same port. Each service must use different ports. 1.4.0 has a regression in this area.
|
Thanks @sdake - no huge urgency on my part, I've patched around it locally. Just don't want other users getting caught out when they upgrade to |
* Resolve regression in tracing Fixes: #19227 The tracing and zipkin services both point to the same workload with the same port. Each service must use different ports. 1.4.0 has a regression in this area. * Use correct port for zipkin service (9411)
Fixes: istio#19227 The tracing and zipkin services both point to the same workload with the same port. Each service must use different ports. 1.4.0 has a regression in this area.
* Resolve regression in tracing Fixes: #19227 The tracing and zipkin services both point to the same workload with the same port. Each service must use different ports. 1.4.0 has a regression in this area. * Use correct port for zipkin service (9411)
* Resolve regression in tracing Fixes: istio#19227 The tracing and zipkin services both point to the same workload with the same port. Each service must use different ports. 1.4.0 has a regression in this area. * Use correct port for zipkin service (9411)
This should resolve the jaeger regression around ports. Additionally other features have been added to the installer. Fixes: istio/istio#19227
|
@Stono this was fixed by an unrelated commit that syncronized the operator with the installer charts after my PR to fix the installer charts had merged for 1.4. Cheers |
|
verified 1.4-dev (what will be 1.4.1) operator instantiates the services as follows Cheers |
This should resolve the jaeger regression around ports. Additionally other features have been added to the installer. Fixes: istio/istio#19227
Fixes: istio#19227 This PR mirrors: istio#19231 I am not confident this change is correct, however, it does revert back to the original 1.3 behavior. I don't understand why we want two services (zipkin and tracing). Should not tracing be sufficient? If we must retain zipkin and we want tracing to run on port 9411 (vs what it has been running on which is port 80...) zipkin must run on some other port.
Bug description
In istio 1.4.0,
tracing.istio-systemhas moved from port80to9411. There is already azipkin.istio-systemservice in the namespace on9411. Both services point to the same workload (Jaeger).This is a breaking change for us so just wondering why it was made and if it was intentional, it should have been in the upgrade notes (as we have upstream systems talking to tracing.istio-system).
Expected behavior
Consistent service ports between releases or details in release notes explaining the changes.
OR if you're really honouring semver releases, 1.4.0 shouldn't have breaking changes from 1.3.x and a different service port could probably be classed as breaking.
Steps to reproduce the bug
Version (include the output of
istioctl version --remoteandkubectl versionandhelm versionif you used Helm)1.4.0
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)
The text was updated successfully, but these errors were encountered: