You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.
Is your feature request related to a problem? Please describe.
The /progress API for POSTing job instance progress updates from k8s sidecars is initially being implemented unauthenticated. This obviously isn't ideal.
Describe the solution you'd like
We should inject some sort of unique auth token into our k8s sidecars which can be used for authn+authz on the /progress endpoint; i.e., the fact that you have the token implies that you are the sidecar (or at least that you have access to it), and therefore you have permission to post progress updates for the corresponding job instance.
Describe alternatives you've considered
Leave it unauthenticated. Not ideal, but not a huge security hole either.
Do full authentication. This might cause progress updates to trigger API rate limiting. Also requires real auth credentials (tokens or tickets) to be available in the sidecar.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The
/progress
API for POSTing job instance progress updates from k8s sidecars is initially being implemented unauthenticated. This obviously isn't ideal.Describe the solution you'd like
We should inject some sort of unique auth token into our k8s sidecars which can be used for authn+authz on the
/progress
endpoint; i.e., the fact that you have the token implies that you are the sidecar (or at least that you have access to it), and therefore you have permission to post progress updates for the corresponding job instance.Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: