#7065 [BUG] CloudWatch link on the Flyte UI for a task is incorrect for binary version Issue created by raweber42 Flyte & Flytekit version Helm chart: flyte-binary v1.16.4 Image: ghcr.io/flyteorg/flyte-binary-release:v1.16.4 Describe the bug When using the flyte-binary chart with CloudWatch logging enabled, the generated CloudWatch link on the Flyte UI for a task is incorrect. The template variables are not resolved - instead of actual values, the link contains literal placeholders like

<AWS_REGION>

and `<EKS_CLUSTER_NAME>`: The region and log group are URL-encoded angle-bracket placeholders (%3C / %3E) instead of the values configured in the Helm values. In the flyte-binary chart, the only logging configuration surface is:

configuration:
  logging:
    plugins:
      cloudwatch:
        enabled: true
        templateUri: |-
          <https://console.aws.amazon.com/cloudwatch/home?region=<my-region>#logEventViewer:group=/aws/eks/<my-cluster>/cluster;stream=var.log.containers.{{> .podName }}_{{ .namespace }}_{{ .containerName }}-{{ .containerId }}.log

The

templateUri

Go template variables (

{{ .podName }}

, etc.) are resolved correctly per-task, but the region and log group are baked into the URI string. Despite this, the rendered link in the UI replaces them with generic

<AWS_REGION>

and

<EKS_CLUSTER_NAME>

placeholders. In contrast, the flyte-core chart exposes a much richer

task_logs.plugins.logs configuration

that has dedicated fields:

task_logs:
  plugins:
    logs:
      kubernetes-enabled: false
      cloudwatch-enabled: true
      cloudwatch-region: "eu-central-2"
      cloudwatch-log-group: "/aws/eks/my-cluster/cluster"
      cloudwatch-template-uri: "..."

These dedicated fields (cloudwatch-region, cloudwatch-log-group) are not available in the flyte-binary chart's configuration.logging schema. It appears the flyte-binary chart only passes through templateUri and ignores (or does not surface) the underlying LogConfig fields that the flyte-core chart supports. The result is that the system falls back to un-resolved placeholder defaults for region and log group. Expected behavior The CloudWatch link rendered in the Flyte UI for each task should use the actual region and log group, either: By correctly resolving the templateUri as-is (since region and log group are already hardcoded in the template string), or By exposing the same task_logs.plugins.logs fields (cloudwatch-region, cloudwatch-log-group, etc.) in the flyte-binary chart so that the non-template-URI code path also works. A correctly rendered link should look like:

<https://console.aws.amazon.com/cloudwatch/home?region=eu-central-2#logEventViewer:group=/aws/eks/my-cluster/cluster;stream=var.log.containers.<pod>_<namespace>_<container>-<id>.log>

(with actual pod/namespace/container/id values substituted per task) Additional context to reproduce 1. Deploy flyte-binary v1.16.4 on EKS with CloudWatch logging configured via configuration.logging.plugins.cloudwatch in Helm values. 2. Register and run any workflow. 3. Click the "Logs" link on any task execution in the Flyte UI. 4. Observe that the CloudWatch URL contains

%3CAWS_REGION%3E and %3CEKS_CLUSTER_NAME%3E

instead of actual values. Screenshots No response Are you sure this issue hasn't been raised already? • Yes Have you read the Code of Conduct? • Yes flyteorg/flyte