Gitops installation need to be able to upgrade between releases

[huang-cn]

• when repo configurations changed between releases, need to find a way to upgrade the gitops configuration as well as the release, might need some test to verify if this is doable.
• is it possible for the gitops install to always just keep a most recent configuration to support all releases, instead of one for one.
• how to "attach" existing installation to gitops? is it possible?

[morningspace]

Since the GitOps configuration (wrapped as helm charts) can evolve separately as opposed to CP4WAIOps itself. A release-to-release upgrade for CP4WAIOps using GitOps, does not only mean to upgrade CP4WAIOps itself, it can also mean to upgrade the GitOps configuration.

For example, after we use GitOps configuration for CP4WAIOps 3.4 to install a CP4WAIOps 3.4 instance, in order to upgrade to 3.5, user can choose to remain the helm chart for GitOps configuration for 3.4 unchanged, but just update the helm values to upgrade CP4WAIOps from 3.4 to 3.5. User can also choose to upgrade the GitOps configuration as well from a helm chart against 3.4 to a newer version that maps to 3.5. Both two scenarios are valid.

In the case of GitOps install method, to upgrade CP4WAIOps release usually means to change the helm values, e.g.: channel value. To upgrade GitOps configuration usually means to change the revision value for the Argo Application. In order to support the smooth upgrade for the GitOps configuration, the helm charts for the GitOps configuration need to be backward compatible from release to release.