Fix: Sanitize user identity before injecting into task pod as K8s label #5023
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
@ByronHsu recently implemented middleware to inject the user identity into the flyte workflow's ExecutionSpec: flyteorg/flyteadmin#549 and in #4637 I injected the user identity into task pods as a label.
For IdPs like Okta, the execution identity is an email address which is not a valid Kubernetes label, causing the creation of the pod to fail.
What changes were proposed in this pull request?
In this PR I add sanitation to the execution identity before injecting it as a label.
How was this patch tested?