This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
--kubeconfig-flag does not work for "component apply" since 8fa88dae #1094
Comments
Should we add this in 0.5.0? |
@iaguis ? |
invidian
added a commit
that referenced
this issue
Oct 19, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
#1018 will fix it, perhaps it could be isolated from this PR, but it is easier to fix this way. |
Yes. |
invidian
added a commit
that referenced
this issue
Oct 19, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Oct 21, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
knrt10
pushed a commit
that referenced
this issue
Oct 22, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
knrt10
pushed a commit
that referenced
this issue
Oct 22, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
knrt10
pushed a commit
that referenced
this issue
Oct 22, 2020
Pass explicity kubeconfig path via options instead. Also fixes #1094. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Surprisingly, it works for "component delete"...
The text was updated successfully, but these errors were encountered: