Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hey y'all

We are running into an interesting problem where if our `flow_run` names are more than `63 characters`, our agent fails to create a deployment run using k8 jobs because it can't create a job label

Will post agent log in thread

```HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Job.batch \"cuttercommunicationsdbagcectelecom-txtx-grays-zj7g6\" is invalid: metadata.labels: Invalid value: \"cuttercommunicationsdbagcectelecom_txtx_grayson_fwa_bdo_filing_\": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')","reason":"Invalid"```

the name of our flow run gets cut off when trying to create a label for our k8 job. In doing so, the agent errors out if the flow run name is more than 63 characters

prefect==2.6.7
python==3.10

using the `prefect.deployments.run_deployment` library

Hm, we should be trimming labels: <https://github.com/PrefectHQ/prefect/blob/main/src/prefect/infrastructure/kubernetes.py#L613>

It looks like the issue here may be that it ends with `_`

(We even have a TODO in the code that we do not handle that yet)

oh I see. thank for pointing that out <@U01CEUST9B5>!

our team is cleaning up the flow run names for now, but if that filtering could be done on the prefect side, that would be great!

<https://github.com/PrefectHQ/prefect/pull/7528>