Sanitizing Kubernetes Labels to Ensure Valid Deployment

Input sanitization and validation is the process of ensuring that data conforms to expected formats and constraints before it is used, especially when interfacing with external systems. This prevents errors, security vulnerabilities, and unexpected behavior by rejecting or transforming invalid inputs. In Kubernetes, labels must adhere to strict character rules, so sanitizing inputs used in labels is critical to avoid deployment failures.

This PR fixes a Helm chart that previously allowed illegal characters (';' and '=') in Kubernetes pod labels generated for multi-team executors. The change extends the existing sanitization logic, which already handled ',' and ':', to also replace these additional forbidden characters. By doing so, the labels become valid Kubernetes identifiers, preventing API server rejections and deployment failures. Meanwhile, the original executor configuration remains intact for application logic, maintaining correct team assignment for edge workers.

Proper input sanitization here ensures that the system deploys reliably and that multi-team executor functionality works as intended. Without it, deployments fail silently or workers don't process tasks, causing operational disruption. This demonstrates how validation at the configuration interface can prevent cascading runtime issues.

Review the sanitization rules applied in this PR and consider other contexts in your projects where input values might be embedded in external system identifiers. How would you design a reusable sanitization utility to handle such cases consistently? Could you extend this Helm chart fix to support additional special characters that might appear in future executor configurations?