A few enhancements to istio-proxy-cfg.py#3235
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:You can indicate your approval by writing |
bin/istio-proxy-cfg.py
Outdated
There was a problem hiding this comment.
We should continue separating yaml files by source(pilot or proxy). It is easy to diff 2 separate files.
There was a problem hiding this comment.
I agree. I was thinking about that while working on it, but hesitating on what command arguments should be used to achieve that. Before this PR, --pilot_url is used to indicate pilot vs proxy. Now that pilot_url is not required, and there are three types of output: pilot, proxy, cache_stats, need a way to write them in different files. Is it ok to define the output argument as --output [DIR]? That way, three files will be written in the directory. Do you have any suggestions or preference? Do you think it's necessary for user to indicate the type of output in the command line?
There was a problem hiding this comment.
Yes output dir sounds good
2d8ad7b to
0bd67a9
Compare
|
/test circleci |
|
/test istio-pilot-e2e |
|
@mandarjog updated per comments. let me know any further comments. thanks |
bin/istio-proxy-cfg.py
Outdated
There was a problem hiding this comment.
nit: its json.. there is no YAML for v1
There was a problem hiding this comment.
I changed the suffix to be json.
|
@mandarjog let me know how to move this forward. thanks. |
Codecov Report
@@ Coverage Diff @@
## master #3235 +/- ##
=======================================
- Coverage 76% 76% -<1%
=======================================
Files 297 297
Lines 26725 27213 +488
=======================================
+ Hits 20254 20536 +282
- Misses 5203 5359 +156
- Partials 1268 1318 +50
Continue to review full report at Codecov.
|
|
Running it directly gets me this error |
|
|
|
Would be good to replace this with "using ${some random local port} for forwarding to pilot" And make it non interactive. |
|
About the curl error, I realized that port-forward can be used and curl can be invoked from the host rather than from inside the container. I'll restructure the code a bit so that both sidecar query and pilot query can use the same code. For local port, I'll use a random port from the range 50000 - 60000, and get rid of the read from user. Let's use another PR for the mtls. |
Add --clear_cache_stats option
to use this command outside the k8s cluster
|
/retest |
1 similar comment
|
/retest |
|
@baodongli: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Made a few enhancements:
Although I think podname as name.namespace.ip or name.namespace is not necessary, I kept them in.