minikube kubectl should always use the profile's minikube context

[didier-viboo]

What Happened?

It's reasonable to expect that when using minikube kubectl, it will only mess with minikube.

I can't think of a reasonable use case where someone would want to use the minikube version of kubectl to mess with a context other than minikube and would have no alternatives.

But I can think of cases where testing scripts run in the wrong context can mess with unintended contexts.

Using minikube kubectl would guarantee against such problems it it was always using the minikube context of the selected profile.

Attach the log file

N/A

Operating System

None

Driver

None

[nirs]

@didier-viboo What do you mean by "using the minikube context?

Minikube supports multiple profiles of arbitrary names, so it cannot limit the minikube kubectl to context "minikube". It also supports multi-nodes clusters that have multiple contexts (name, name-m02, ...).

Maybe you mean that the command should work only if we have a minikube profile with the same name as the --context argument?

The problem is that kubectl cannot be limited to certain minikube profile, some commands like kubectl config do not work on a single context.

Also why there is a need to limit the scope of the minikube kubectl command? this command is not installed in the PATH so it does not affect usage of standard kubectl command installed in the PATH (e.g /usr/local/bin).

[nirs]

@medyagh Can we enable GitHub discussions for this project? It is a better place for such discussions.

[didier-viboo]

@didier-viboo What do you mean by "using the minikube context?

Minikube supports multiple profiles of arbitrary names, so it cannot limit the minikube kubectl to context "minikube". It also supports multi-nodes clusters that have multiple contexts (name, name-m02, ...).

Maybe you mean that the command should work only if we have a minikube profile with the same name as the --context argument?

The problem is that kubectl cannot be limited to certain minikube profile, some commands like kubectl config do not work on a single context.

Also why there is a need to limit the scope of the minikube kubectl command? this command is not installed in the PATH so it does not affect usage of standard kubectl command installed in the PATH (e.g /usr/local/bin).

There are contexts which point at minikube instances and contexts which don't.

My point is that when using minikube kubectl to access a context not pointing at a minikube instance it should fail.