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

remove the internal-objects annotation for gitopsservice

    • 1
    • False
    • False
    • Hide
      * Previously, the `gitopsservice` service was annotated as an internal object. This update removes the annotation so you can update or delete the default Argo CD instance and run GitOps workloads on infrastructure nodes by using the UI. link:https://issues.redhat.com/browse/GITOPS-1429[GITOPS-1429]
      Show
      * Previously, the `gitopsservice` service was annotated as an internal object. This update removes the annotation so you can update or delete the default Argo CD instance and run GitOps workloads on infrastructure nodes by using the UI. link: https://issues.redhat.com/browse/GITOPS-1429 [ GITOPS-1429 ]
    • GITOPS Sprint 208

      https://github.com/redhat-developer/gitops-operator/issues/239

       

      Acceptance Criteria

      1. Can enable the feature to run workloads on Infra node from UI.
      2. Delete the default Argo CD instance from the UI.

            [GITOPS-1429] remove the internal-objects annotation for gitopsservice

            Please provide further feedback on this release note item in the following PR: https://github.com/openshift/openshift-docs/pull/40738/files

            Further changes to the release note in this Jira will not be migrated to the PR.

            aveerama@redhat.com, please specify which UI the release note is referring to.

            Rolfe Dlugy-Hegwer added a comment - Please provide further feedback on this release note item in the following PR: https://github.com/openshift/openshift-docs/pull/40738/files Further changes to the release note in this Jira will not be migrated to the PR. aveerama@redhat.com , please specify which UI the release note is referring to.

            I think this one needs release notes.

            Jann Fischer added a comment - I think this one needs release notes.

            Jira is tagged for release v1.4, so this change can directly go into the master branch. I have raised PRs for both v1.3 and master, I think we can close the PR for v1.3 with comments.

            PR for master: https://github.com/redhat-developer/gitops-operator/pull/240
            PR for v1.3: https://github.com/redhat-developer/gitops-operator/pull/241  [I am closing this as Jira is targeted for v1.4]

            Abhishek Veeramalla added a comment - Jira is tagged for release v1.4, so this change can directly go into the master branch. I have raised PRs for both v1.3 and master, I think we can close the PR for v1.3 with comments. PR for master: https://github.com/redhat-developer/gitops-operator/pull/240 PR for v1.3: https://github.com/redhat-developer/gitops-operator/pull/241   [I am closing this as Jira is targeted for v1.4]

            Has this been fixed with v1.3, or do we need to pull it into 1.3.1?

            Jann Fischer added a comment - Has this been fixed with v1.3, or do we need to pull it into 1.3.1?

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

                Created:
                Updated:
                Resolved: