acoustic-carpenter-78188
04/18/2026, 6:00 PMflyte-binary chart only exposed templateUri for CloudWatch log configuration, requiring users to embed the AWS region and EKS cluster name directly in a URL template string. The eks example files shipped with literal <AWS_REGION> and <EKS_CLUSTER_NAME> placeholder strings. When users deployed without replacing these, the placeholders appeared URL-encoded (%3CAWS_REGION%3E) in the Flyte UI CloudWatch log links.
The flyte-core chart supports dedicated cloudwatch-region and cloudwatch-log-group fields, which the backend uses to construct the CloudWatch URL internally. The flyte-binary chart lacked equivalent fields.
What changes were proposed in this pull request?
• charts/flyte-binary/values.yaml: Added cloudwatch.region and cloudwatch.logGroup fields under configuration.logging.plugins.cloudwatch.
• charts/flyte-binary/templates/_helpers.tpl: Updated the flyte-binary.configuration.logging.plugins helper to emit cloudwatch-region and cloudwatch-log-group when the new fields are set. The existing templateUri field takes precedence when set, preserving full backward compatibility.
• charts/flyte-binary/eks-production.yaml and eks-starter.yaml: Replaced the templateUri with the placeholder strings with the new region and logGroup fields, which users replace with their actual values.
How was this patch tested?
Verified with helm template that:
• Setting cloudwatch.region and cloudwatch.logGroup produces cloudwatch-region and cloudwatch-log-group config keys in the rendered configmap.
• Setting cloudwatch.templateUri still produces cloudwatch-template-uri as before (backward-compatible path).
Labels
• fixed
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
flyteorg/flyteacoustic-carpenter-78188
04/23/2026, 10:22 AM