Closed nicole-lihui closed 5 months ago
personally, I think the plus istioctl analyze --revision
should be consistent withisitoctl ps --revison
personally, I think the plus
istioctl analyze --revision
should be consistent withisitoctl ps --revison
$ istioctl ps --revision canary
NAME CLUSTER CDS LDS EDS RDS ECDS ISTIOD VERSION
sleep-6fcc95dddf-fgx7v.test-ns Kubernetes SYNCED SYNCED SYNCED SYNCED NOT SENT istiod-canary-78648569f6-6vmch 1.18.6
$ istioctl ps --revision bule
NAME CLUSTER CDS LDS EDS RDS ECDS ISTIOD VERSION
istio-ingressgateway-5f6b58d4b5-nvsv7.istio-system Kubernetes SYNCED SYNCED SYNCED NOT SENT NOT SENT istiod-bule-66d5d8bd5f-ms48t 1.18.6-test
sleep-69cfb4968f-dsx9j.test-bule Kubernetes SYNCED SYNCED SYNCED SYNCED NOT SENT istiod-bule-66d5d8bd5f-ms48t 1.18.6-test
I think that currently, there are some base resources such as services, namespaces, and pods that are used for resource discovery. These exist in the analysis without relating to the revision. As you can see, you have same outputs for different --revision
that include both services and namespaces.
🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2024-01-31. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
Is this the right place to submit this?
Bug Description
Issue Description:
When utilizing the
istioctl analyze --revision canary -A
command, it was observed that the analysis did not follow the specified--revision
parameter; instead, it provided output for all relevant information.Version
Additional Information
No response