Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-6707

Host name error for ApplicationSet Webhook Server route

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Before this update, OpenShift Route resource creation for the ApplicationSet webhook server would fail when ArgoCD instances had long names that exceeded Kubernetes label limits (63 characters) or hostname limits (253 characters). This caused route creation to fail with validation errors, preventing ApplicationSet webhook functionality from working properly. With this update, this issue is fixed by implementing intelligent truncation logic that safely shortens generated route names and hostnames while preserving uniqueness and ensuring they remain within the allowed character limits. Now, ArgoCD instances with long names can successfully create ApplicationSet webhook server routes without encountering validation errors, ensuring ApplicationSet webhook functionality works correctly regardless of the ArgoCD instance name length.
      Show
      Before this update, OpenShift Route resource creation for the ApplicationSet webhook server would fail when ArgoCD instances had long names that exceeded Kubernetes label limits (63 characters) or hostname limits (253 characters). This caused route creation to fail with validation errors, preventing ApplicationSet webhook functionality from working properly. With this update, this issue is fixed by implementing intelligent truncation logic that safely shortens generated route names and hostnames while preserving uniqueness and ensuring they remain within the allowed character limits. Now, ArgoCD instances with long names can successfully create ApplicationSet webhook server routes without encountering validation errors, ensuring ApplicationSet webhook functionality works correctly regardless of the ArgoCD instance name length.
    • GitOps Tangerine Sprint 15, GitOps Tangerine Sprint 16, GitOps Tangerine Sprint 17, GitOps Tangerine Sprint 18

      Description of Problem

      • The default hostname generated after enabling `applicationSet.webhookServer.route` is throwing below error:
        ~~~
         - lastTransitionTime: "2025-04-07T20:05:29Z"
              message: 'Route.route.openshift.io "openshift-gitops-applicationset-controller-webhook"
                is invalid: spec.host: Invalid value: "openshift-gitops-applicationset-controller-webhook-openshift-gitops.<apps.url>":
        ~~~

      Additional Info

      • <Any additional info such as logs, must-gather outputs, etc.>

      Problem Reproduction

      • <How do we reproduce the problem?>

      Reproducibility

      • <Always/Intermittent/Only Once>

      Prerequisites/Environment

      • <OpenShift, managed service (e.g., ROSA, ARO), operators, layered product, and other software versions, build details>

      Steps to Reproduce

      • ...

      Expected Results

      • ...

      Actual Results

      • ...

      Problem Analysis

      • <Completed by engineering team as part of the triage/refinement process>

      Root Cause

      • <What is the root cause of the problem? Or, why is it not a bug?>

      Workaround (If Possible)

      • <Are there any workarounds we can provide to the customers?>

      Fix Approaches

      • <If we decide to fix this bug, how will we do it?>

      Acceptance Criteria

      • ...

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Ensure code coverage is not reduced with the changes.
        • Integration tests have been automated.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested and merged on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written (if applicable).
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
        • Midstream changes (if applicable) are done, reviewed, approved and merged.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.

              rh-ee-atali Atif Ali
              rhn-support-jyarora Jyotsana Arora
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: