Invalid kube-config file. Expected key user in kube-config/users[name=xxx]

[xychu]

Got Invalid kube-config file. Expected key user in kube-config/users[name=admin] when use
kube-config file like:

apiVersion: v1
clusters:
- cluster:
    insecure-skip-tls-verify: true
    server: http://192.168.56.102:8080
  name: vm
contexts:
- context:
    cluster: vm
    user: admin
  name: vm
current-context: vm
kind: Config
preferences: {}
users:
- name: admin
  user: {}

or

apiVersion: v1
clusters:
- cluster:
    insecure-skip-tls-verify: true
    server: http://192.168.56.102:8080
  name: vm
contexts:
- context:
    cluster: vm
    user: admin
  name: vm
current-context: vm
kind: Config
preferences: {}
users:
- name: admin

but kubectl works well with both content.

[daicang]

I met this problem when using an old version(2.0.0) of python client, and solving by upgrading to 6.0.0. Maybe you could check the client version.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pacoxu]

I met same problem too.

python3 + kubernetes (10.0.1)

kind: Config
clusters:
- name: local
  cluster:
    server: http://127.0.0.1:8080
users:
- name: xxx
contexts:
- context:
    cluster: local
    user: xxx
  name: xxx-context
current-context: xxx-context

error stack:

config.kube_config.load_kube_config(config_file=config_file_path)

File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 645, in load_kube_config
persist_config=persist_config)
File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 613, in _get_kube_config_loader_for_yaml_file
**kwargs)
File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 153, in init
self.set_active_context(active_context)
File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 181, in set_active_context
self._user = user['user']
File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 499, in getitem
% (key, self.name))
kubernetes.config.config_exception.ConfigException: Invalid kube-config file. Expected key user in /etc/kubernetes/xxx.conf/{'name': 'kubelet'}

[pacoxu]

/reopen

[k8s-ci-robot]

@pacoxu: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Skyler1017]

met same issue