-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ztunnel-config might not be printing out ztunnel data correctly #50807
Comments
The unit test shows the logic is fine assuming that the bytes to be unmarshalled contain the right fields. It seems my local environment does not produce the right data (confirmed by curling localhost:15000/config_dump and also by printing it out as shown in the draft PR linked above). Does not match the example of expected data structure in testdata/dump.json. |
Link to output I'm seeing for my cluster: https://docs.google.com/document/d/1uwN0EWQNu7-T5POPodRW4Bnio86ZLZBW1LjnVBILuqo/edit?usp=sharing Created my cluster following these steps: https://istio.io/latest/docs/ops/ambient/getting-started/ Istioctl generated from latest Istio branch. Ran |
We should probably have a schema or proto in both spots for this, or at least an istio-side integ test. |
are you on latest version of both? it works for me. We changed the keys a while back |
Ok, good! Wdym, when you say latest version of both @howardjohn ? The istio repo and ztunnel repo I have locally is as up to date as today, but maybe you're referring to something else? |
I think my ztunnel binary was out of date, this is a non-issue |
Is this the right place to submit this?
Bug Description
draft PR #50806 describes this in detail with examples.
The ztunnel config dump writer does not appear to be getting the ztunnel config dump and unmarshalling that into the ztunnelDump struct correctly within the istioctl code. I think it's causing issues with how this data gets printed for commands like
istioctl x ztunnel-config workload
Version
Additional Information
#50806
The text was updated successfully, but these errors were encountered: