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

ArgoCD Server Options - Service.Type=NodePort not applied to service

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • Hide
      Before this update, when the desired stated for the server service type changed (from ClusterIP to NodePort), it wasn't applied to the cluster automatically without deleting the resource. This update fixes the issue by adding the Server Service check to apply the changes in case the service exists. Now, if the desired stated for the server service type changes it's applied to the cluster automatically without deleting the resource, just updating it.
      Show
      Before this update, when the desired stated for the server service type changed (from ClusterIP to NodePort), it wasn't applied to the cluster automatically without deleting the resource. This update fixes the issue by adding the Server Service check to apply the changes in case the service exists. Now, if the desired stated for the server service type changes it's applied to the cluster automatically without deleting the resource, just updating it.
    • 5
    • GitOps Crimson - Sprint 3262, GitOps Crimson - Sprint 3263

      Description of problem:

      I tried modifying the service type of argocd-server from ClusterIP to NodePort. After applying the manifest, the service type is still ClusterIP instead of NodePort.

      Complete details of the issue - https://github.com/argoproj-labs/argocd-operator/issues/1390

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

      NA

      Steps to Reproduce

      Please refer to https://github.com/argoproj-labs/argocd-operator/issues/1390

      Actual results:

      Expected results:

      Argo CD Server should be updated to the service of type NodePort through the above mentioned configuration in the GitHub issue.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      • Create a PR to the Argo CD Operator repo.
      • Bring the changes to the GitOps operator.
      • Add a release note item to explain that the bug is fixed.

       

      Definition of Done:

      Build Details:

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

       

       *

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

                Created:
                Updated:
                Resolved: