If you specify any cloud provider through flags, it will be used by kubelet (see https://github.com/kubernetes/kubernetes/blob/release-1.3/pkg/kubelet/kubelet.go#L1068). It's only when you don't specify any cloud provider that kubelet will detect the cloud provider from the machine info, as described by the comment.

        // If no cloud provider is defined - use the one detected by cadvisor

that's exactly my situation, I want to run in our private cloud environment without any of the cloud integration. If I specify cloud-provider="" at runtime it will get overridden.

that's exactly my situation, I want to run in our private cloud environment without any of the cloud integration. If I specify cloud-provider="" at runtime it will get overridden.

Ah I see. I guess specifying an empty string is the same as not specifying any cloud provider.

This auto-detection feature was introduced by #21373
/cc the author and reviewer to see if this is an intended behavior: @enoodle @vishh

@emaildanwilson Legitimate concern. I'm posting a fix. Do you consider this to be a regression or are you just getting started with k8s.

@yujuhong @vishh I am sorry, This was not the original intention. We can keep the auto detection with a flag, or make a flag to ask kubelet not to do it.
Unless there is a way to see if the variable was assigned to that I missed.
I can post a fix tomorrow if it won't exit by then.

@vishh Thank you. We're running on 1.2.4 and won't be running on 1.3 for a few months yet anyways and was just testing to look for future issues when I found this.

@vishh I assigned this issue to you since you are working on a fix, and I can't assign this to @enoodle anyway :-)

@emaildanwilson Thanks for testing our 1.3 release candidate, and reporting this regression to us. We are including the fix to 1.3.