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

Changing host in the Argo CD CR does not update the ingress configuration

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • Hide
      Before this update, when the desired stated for an existing Ingress changed the host, it wasn't updated with the new host information. This update fixes the issue by adding the Ingress checks to apply the changes in case it exists. Now, if there is a change in the ingress host it's updated with the new value.
      Show
      Before this update, when the desired stated for an existing Ingress changed the host, it wasn't updated with the new host information. This update fixes the issue by adding the Ingress checks to apply the changes in case it exists. Now, if there is a change in the ingress host it's updated with the new value.
    • GitOps Crimson - Sprint 3262, GitOps Crimson - Sprint 3263

      Description of problem:

      Changing host in the Argo CD CR for Argo CD Server does not update the ingress configuration.

      Complete details here - https://github.com/argoproj-labs/argocd-operator/issues/558

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      Do a kubectl apply on something like:

      ```yaml
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      metadata:
        name: argocd
      spec:
        server:
          ingress:
            enabled: true
      ```

      followed by a kubectl apply on something like:

      ```yaml
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      metadata:
        name: argocd
      spec:
        server:
          host: foo.bar

          ingress:
            enabled: true
      ```

      then the host will still be set to the default value when describing the ingress.

      Actual results:

      Expected results:

        • Changing host in the Argo CD CR should update the ingress configuration*

          Reproducibility (Always/Intermittent/Only Once):

          Always

          Acceptance criteria: 

      • Fix the issue in the Argo CD Operator.
      • Add tests to validate the change (Unit and E2E)
      • Bring the changes to the downstream - GitOps Operator along with the tests.
      • Document the fix in the release notes.

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              nmirasch@redhat.com Neus Miras Chueca
              aveerama@redhat.com Abhishek Veeramalla
              Neus Miras Chueca
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 5 minutes
                  5m
                  Remaining:
                  Remaining Estimate - 5 minutes
                  5m
                  Logged:
                  Time Spent - Not Specified
                  Not Specified