Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-2325

CCM-AWS upstream: implement target group attributes configuration for Traffic Control

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • Product / Portfolio Work
    • None
    • Hide

      2025.08.29:

      Show
      2025.08.29: PR approved by Cloud and AWS Team PR merged 2025.08.26: PR reviewed by AWS team 2025.08.25: Awaiting PR review from maintainers 2025.08.20: Awaiting PR review from maintainers 2025.08.15: Marco implemented the suggestion by introducing pre-flight checks for EnsureLoadBalancer to validate constraints of Service before calling API, making confidence when changing cloud resource, and isolating scope of failures. PR sent back to reviewers. 2025.08.14: Found consensus about error handling. 2025.08.13: Marco asked more information about expected behavior in the controller when found failures 2025.08.11: PR reviewed by Cloud team SPLAT addressed the feedback and send back to review. 2025.08.07: Marco asked for help/review on slack: https://redhat-internal.slack.com/archives/CBZHF4DHC/p1754599200795649 2025.07.29: Awaiting to have kops binary with the recent changes adding the permissions. Check the comment for more information: https://github.com/kubernetes/cloud-provider-aws/pull/1214#issuecomment-3134206724 2025.07.29: Permissions fixes merged on kops. I am checking if CCM-AWS CI uses main stream. 2025.07.28: Permission fixes submtited to k/kops repo https://github.com/kubernetes/kops/pull/17521 2025.07.25: The PR is blocked awaiting for CI permission fixes. 2025.07.24: increased verbosity in the PR and discovered the CI permission limitations. We need to submit this change to the CCm-AWS CI infra. I asked teams on Slack: https://issues.redhat.com/browse/SPLAT-2344?focusedId=27667513&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27667513 2025.07.18 - Waiting for feedback from CIO team about enough changes on CCM based in the PR https://github.com/kubernetes/cloud-provider-aws/pull/1214
    • False
    • 13
    • 8
    • None
    • None
    • OpenShift SPLAT - Sprint 274, OpenShift SPLAT - Sprint 275, OpenShift SPLAT - Sprint 276

      {}USER STORY:{}

      • As an OpenShift engineer, I want to expose the target group attributes related to "Traffic Control" so that users can workaround of hairpin connection issue in private clusters
      • As an OpenShift engineer, I want to expose the target group attributes related to "Traffic Control" so that Cluster Ingress Operator can decide when enabling Proxy to the router when deploying private clusters to resolve the hairpin connection issue

      {}DESCRIPTION:{}

       

      {}Required:{}

      • PR proposing to change the target group attributes for traffic control used to fix the hairpinning traffic on NLB
      • e2e tests exercising the configuration

      {}Nice to have:{}

      ...

      {}ACCEPTANCE CRITERIA:{}

      • PR merged on CCM fixing the hairpinning connection issue by exposing the annotation to configure the traffic control attributes of Target Group
      •  
      •  

      {}ENGINEERING DETAILS:{}

      <!--

      Any additional information that might be useful for engineers: related
      repositories or pull requests, related email threads, GitHub issues or
      other online discussions, how to set up any required accounts and/or
      environments if applicable, and so on.

      -->

              rhn-support-mrbraga Marco Braga
              rhn-support-mrbraga Marco Braga
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: