-
Notifications
You must be signed in to change notification settings - Fork 117
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
feat: allow arbitrary length API tokens #752
base: main
Are you sure you want to change the base?
Conversation
Hey @kamushadenes, I will respond here, but the same applies to the other two PRs: This sounds very interesting. I am not sure if a flag is necessary, or if we just want to the whole validation. I will talk to the team responsible for tokens next week and will report back afterwards. |
Hey @kamushadenes, we talked about this today internally. We would prefer not to add any additional flags or environment variables to disable the check. We also do not think that the check is strictly necessary. Instead we would prefer to change the errors when Do you want to update your PRs to log warnings or should we do work on that? |
Hey @apricote, thanks for getting back! Makes total sense, I'll update the PRs in a couple hours when my day starts. |
Done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was about to leave a comment regarding the unit test :D
Do not worry about the e2e tests, they do not work for PRs from forks.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #752 +/- ##
==========================================
- Coverage 72.00% 71.73% -0.27%
==========================================
Files 31 30 -1
Lines 2650 2473 -177
==========================================
- Hits 1908 1774 -134
+ Misses 553 525 -28
+ Partials 189 174 -15 ☔ View full report in Codecov by Sentry. |
Context
We have developed a soon-to-be-open-source proxy that forces specific labels in order to provide scoped API access, and that doesn't expose the real API token. This was created to have better control of resources inside the same project (as API tokens currently lack granularity), and to be able to use a single project securely, given that it isn't possible to create a project via the API.
One of it's operating modes is using JWT as a virtual self-validating token, which can't have a fixed size.
This support is required to make full use of it inside a Kubernetes cluster.
The feature is behind a default-false flag so it shouldn't interfere with current behavior.
Related
kubernetes/autoscaler#7285
hetznercloud/csi-driver#724