Open googlebabaio opened 1 year ago
Thank you for your contribution to the Volcano community. This problem recurs locally. Currently, vcctl does not apply the namespace configuration in kubeconfig. Instead, it is specified by command-line parameters.
I tried to fix the problem.
Thanks. Because we think the reason for using vcctl is to simplify the complexity of kubectl commands, just like helm. In other words, using kubectl is sufficient if not simplified.
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Retain the current issue.
/assign @wangyang0616
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
/remove lifecycle/stale
What happened: vcctl not use kubeconfig
What you expected to happen: Use the kubeconfig file
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):1.21.2uname -a
):3.10.0-1160.53.1.el7.x86_64