Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubernetes.client.AuthenticationV1TokenRequest() fails #2250

Open
jhourque opened this issue Jun 24, 2024 · 2 comments
Open

kubernetes.client.AuthenticationV1TokenRequest() fails #2250

jhourque opened this issue Jun 24, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jhourque
Copy link

What happened (please include outputs or screenshots):
In documentation, the example given for api create_namespaced_service_account is not working due to:
body = kubernetes.client.V1ServiceAccount()

Traceback (most recent call last):
File "t.py", line 87, in
body = kubernetes.client.AuthenticationV1TokenRequest() # AuthenticationV1TokenRequest |
File "/usr/local/lib/python3.7/site-packages/kubernetes/client/models/authentication_v1_token_request.py", line 70, in init
self.spec = spec
File "/usr/local/lib/python3.7/site-packages/kubernetes/client/models/authentication_v1_token_request.py", line 160, in spec
raise ValueError("Invalid value for spec, must not be None") # noqa: E501
ValueError: Invalid value for spec, must not be None

(Nota: code indentation id wrong, but the issue is still there even while fixing it)

What you expected to happen:
The call to create_namespaced_service_account should work but the example is stuck before this call

How to reproduce it (as minimally and precisely as possible):
Copy paste example given : https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md#create_namespaced_service_account_token
(adapt code to be connect to your cluster)

Anything else we need to know?:
I made a test with api list_namespace and list_namespaced_service_account they don't require call to AuthenticationV1TokenRequest and they are working well.

I presume that spec parameter should be set but I don't know what to set without a good example.

Environment:

  • Kubernetes version (kubectl version): 1.29
  • OS (e.g., MacOS 10.13.6): Linux (amazon linux EC2)
  • Python version (python --version) 3.7
  • Python client version (pip list | grep kubernetes) 26.1.0
@jhourque jhourque added the kind/bug Categorizes issue or PR as related to a bug. label Jun 24, 2024
@jhourque
Copy link
Author

jhourque commented Jun 25, 2024

I found the solution. We need to add body with audience and expiration_seconds:
spec = kube.client.V1TokenRequestSpec(audiences=['https://kubernetes.default.svc'], bound_object_ref=None, expiration_seconds=<expiration in seconds>) body = kube.client.AuthenticationV1TokenRequest(spec=spec) response = api_instance.create_namespaced_service_account_token(name=name, namespace=ns, body=body)

It also would be nice to explain that name is the service account name.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants