You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that k8sgpt is inconsistent with how kubectl handle this.
Current behavior is k8sgpt does not respect $KUBECONFIG env. You should manually copy the path of kubeconfig and pass --kubeconfig flag every time when you switch the context, which significantly decrease overall UX.
Before, the default value set for the `--kubeconfig` flag prevented the
`KUBECONFIG` env variable to be ever taken into consideration. This
behavior has now been fixed.
If `--kubeconfig` flag is set, it takes precedence over the `KUBECONFIG` env
variable.
fixesk8sgpt-ai#331
Signed-off-by: Patrick Pichler <git@patrickpichler.dev>
Before, the default value set for the `--kubeconfig` flag prevented the
`KUBECONFIG` env variable to be ever taken into consideration. This
behavior has now been fixed.
If `--kubeconfig` flag is set, it takes precedence over the `KUBECONFIG` env
variable.
fixesk8sgpt-ai#331
Signed-off-by: Patrick Pichler <git@patrickpichler.dev>
Before, the default value set for the `--kubeconfig` flag prevented the
`KUBECONFIG` env variable to be ever taken into consideration. This
behavior has now been fixed.
If `--kubeconfig` flag is set, it takes precedence over the `KUBECONFIG` env
variable.
fixes#331
Signed-off-by: Patrick Pichler <git@patrickpichler.dev>
Co-authored-by: Patrick Pichler <git@patrickpichler.dev>
Checklist:
Is this feature request related to a problem?
On first try, I couldn't able to run k8sgpt:
Even
$KUBECONFIG
is set and context is correct:This means that k8sgpt is inconsistent with how kubectl handle this.
Current behavior is k8sgpt does not respect
$KUBECONFIG
env. You should manually copy the path of kubeconfig and pass--kubeconfig
flag every time when you switch the context, which significantly decrease overall UX.Expected behavior:
Describe the solution you'd like
Respect
$KUBECONFIG
env (if set) and it should be first precedence. (like how kubectl did)Benefits for the project and its users
Consistency and better UX.
Potential drawbacks
It would be a backward-incompatible behavior.
Additional context
-
The text was updated successfully, but these errors were encountered: