You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a WorkloadEntry generated from istioctl workload entry configure ... appears on the graph, the version displayed is always "latest" despite properly labeling the WorkloadGroup and WorkloadEntry objects with e.g. version: v1.
Versions used
Kiali: 1.36
Istio: 1.10
Kubernetes flavour and version: 1.21
To Reproduce
Steps to reproduce the behavior:
Add a WorkloadEntry VM to the mesh with a version label and send traffic to it
Navigate to the graph and observe the node with "latest" as its version.
Expected behavior
Expected to see the graph node for the WorkloadEntry workload to display the proper version.
Note telemetry has the wrong source_canonical_revision="latest" label but the right version="v1" label.
The cause for this seems to be that when the workload entry VM files are created with istioctl workload entry configure, the "service.istio.io/canonical-version" label gets generated but not the "service.istio.io/canonical-revision" label.
It might be possible for Kiali to use both source_canonical_revision and service_istio_io_canonical_revision as service_istio_io_canonical_revision is correctly labeled with the right version?
The text was updated successfully, but these errors were encountered:
To me this seems like an Istio reporting bug and not a Kiali bug. The canonical_revision should not be "latest" when there is a version label set to "v1". The canonical_revision should be set to the value of, in this order of preference:
service.istio.io/canonical-revision
app.kubernetes.io/version
version
"latest"
If the workaround works that's a good alternative until the issue is resolved. I'm going to label this waiting-external until we know what Istio says about this...
Describe the bug
When a
WorkloadEntry
generated fromistioctl workload entry configure ...
appears on the graph, the version displayed is always "latest" despite properly labeling theWorkloadGroup
andWorkloadEntry
objects with e.g.version: v1
.Versions used
Kiali:
1.36
Istio:
1.10
Kubernetes flavour and version:
1.21
To Reproduce
Steps to reproduce the behavior:
WorkloadEntry
VM to the mesh with a version label and send traffic to itExpected behavior
Expected to see the graph node for the
WorkloadEntry
workload to display the proper version.Note telemetry has the wrong
source_canonical_revision="latest"
label but the rightversion="v1"
label.The cause for this seems to be that when the workload entry VM files are created with
istioctl workload entry configure
, the"service.istio.io/canonical-version"
label gets generated but not the"service.istio.io/canonical-revision"
label.mesh.yaml
This may be more of an upstream issue but I wanted to post the workaround here in case others run into this same issue.
Workaround
A workaround is to add the
"service.istio.io/canonical-revision"
to yourWorkloadGroup
/WorkloadEntry
objectsIt might be possible for Kiali to use both
source_canonical_revision
andservice_istio_io_canonical_revision
asservice_istio_io_canonical_revision
is correctly labeled with the right version?The text was updated successfully, but these errors were encountered: