failiure to parse a kube config with auth-provider expiry

[clux]

A ~/.kube/config with a user using an auth-provider seems to fail to parse atm:

Excerpt:

- name: provider-name
  user:
    auth-provider:
      config:
        access-token: foo
        apiserver-id: serverguid
        client-id: clientguid
        expires-in: "3600"
        expires-on: "1537526210"
        refresh-token: token
        tenant-id: tenantguid

causes:

  File "/home/clux/app/venv/lib/python3.7/site-packages/kubernetes/config/kube_config.py", line 504, in load_kube_config
    loader.load_and_set(config)
  File "/home/clux/app/venv/lib/python3.7/site-packages/kubernetes/config/kube_config.py", line 385, in load_and_set
    self._load_authentication()
  File "/home/clux/app/venv/lib/python3.7/site-packages/kubernetes/config/kube_config.py", line 183, in _load_authentication
    if self._load_auth_provider_token():
  File "/home/clux/app/venv/lib/python3.7/site-packages/kubernetes/config/kube_config.py", line 198, in _load_auth_provider_token
    return self._load_azure_token(provider)
  File "/home/clux/app/venv/lib/python3.7/site-packages/kubernetes/config/kube_config.py", line 208, in _load_azure_token
    if int(provider['config']['expires-on']) < time.gmtime():
TypeError: '<' not supported between instances of 'int' and 'time.struct_time'

on load_kube_config()

[tomplus]

It's addressed here: kubernetes-client/python-base#84

[brichins]

Any traction or update on this issue?

[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.