Atsushi
Atsushi
I have same error. Is there any update for this issue? I'm using `argo: v2.9.3`.
> Argo, both CLI and Controller 2.4.0+ FYI When revert argo to v2.4.0 and run the following setup for argo, it works on my local k8s cluster. ``` kubectl create...
/az start
Thanks for your PR. Currently our test environment on Azure Pipeline seems to have a problem. We're looking at this issue.
I'd like to work on this issue if it's not been handled by anyone yet. @MaruthiKo @aiyushbedi007 @vladklokun
As far as I did a quick look for kinda of cache in the source code, I find `DefaultLocalStore` which is specified by `KS_CACHE_DIR`, it seems not to be a...
Sorry about no update for months. I can hand it over to you @0xt3j4s Thanks.
I added `context` flag as follow:  And I've not added `ARGOCD_CONTEXT` yet because I'm not sure using environment variable manner has consistency with other flags. Should I work on...
@wtam2018 Thank you for the review. No, there is no other than this one line change. In my understanding, basically `Context` in `ClientOptions` is expected that it's empty unless you...
I also noticed from one [failure](https://github.com/argoproj/argo-cd/runs/3989537187?check_suite_focus=true) in CI that the newly added `--context` flag is conflicted with some other existing `--context` which come from kubectl flag (e.g. `argocd admin settings...