Feature: Update Argocd from 2.10 to 2.14.5

[csantanapr]

Have you searched for this feature request?

• I searched but did not find similar requests

Problem Statement

The version of ArgoCD that comes with idpbuilder, it would be good to update to the latest version.

Possible Solution

update the argocd stored with latest version

Alternatives Considered

No response

[csantanapr]

How easy is to do this, are there any docs a new contributor can use to complete this task?

[cmoulliard]

How easy is to do this, are there any docs a new contributor can use to complete this task?

I don't think that the process is documented. To bump a core component (argocd, gitea, ingress), it is needed to:

• Figure out how the resources are generated part of the hack folder. Example for argocd: https://github.com/cnoe-io/idpbuilder/tree/main/hack/argo-cd
• Bump the version part of the kustomization file: https://github.com/cnoe-io/idpbuilder/blob/main/hack/argo-cd/kustomization.yaml#L4
• Review the patched files to see if changes (new file or files to be deleted or files to be changed, etc) are needed: https://github.com/cnoe-io/idpbuilder/blob/main/hack/argo-cd/kustomization.yaml#L7-L16
• Generate the new resources YAML files
• Review the cnoe argocd api project if types changed - https://github.com/cnoe-io/argocd-api !!
• Build a new idpbuilder locally
• Test it locally like also using CI tests - Github Workflow(s)
• Update the documentation to detail which version of argocd, gitea, ingress, kind is used part of idpbuilder version or range of versions etc

[csantanapr]

Thanks, where do we document the current versions included in idpbuilder?

[cmoulliard]

Thanks, where do we document the current versions included in idpbuilder?

This is not documented at all part of the release note https://github.com/cnoe-io/idpbuilder/releases or as table part of the README.md (or cnoe.io doc web site).

There is a ticket which has been created to automate such a process: #382 but I don't think that it makes sense to automate such a process instead of having a table this updated manually when release includes bump of version for a core component

[csantanapr]

I agree no need to automate it, if its simply 2 core packages

[csantanapr]

@cmoulliard could you open a PR to doc these steps in https://github.com/cnoe-io/idpbuilder/blob/main/CONTRIBUTING.md