Update argocd to v2.5.0

Package Merge Request

Package Changes

https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/blob/5.13.0-bb.0/CHANGELOG.md

Package MR

https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/merge_requests/111

https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/merge_requests/106

For Issue

Closes https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/issues/62

added argocd botmr statusreview labels

assigned to @project_2872_bot2

changed the description

requested review from @micah.nagel, @BrandenCobb, @ryan.j.garcia, and @rob.ferguson

assigned to @lucas.rodriguez

changed the description

marked this merge request as ready

changed title from Draft: Updated argocd git tag to Update argocd to v2.5.0

Should be good to go. The upgrade cypress test is broke, but this new tag should fix it.

resolved all threads

approved this merge request

resolved all threads

unapproved this merge request

Trying to wrap my head around the docs changes for keycloak/sso. Previously the purpose of that doc was focused on production/customer SSO config. I'm not sure how accurate it was but it looks like the intent got changed to a focus on development? I'd prefer we keep the main keycloak doc focused on production still...we can add developer docs for SSO testing too, just want to make sure we don't lose anything.

Sidenote: For developer Argo SSO, any reason to not just document the process with the dev client/login.dso.mil. Spinning up keycloak is a bit overkill for this use case imo.

Might need a release note for this?

This version introcudes new configs.cm and configs.rbac sections that replaces server.config and server.rbacConfig respectively. Please move your current configuration to the new place. The Argo CD RBAC config now also sets defaults in the argocd-rbac-cm. If you have manually created this ConfigMap please ensure templating is disabled so you will not lose your changes.

I also noticed a change to a few securityContexts...

controller:
  containerSecurityContext:
    runAsUser: 1000
    runAsGroup: 1000

User/group got removed from this one.

dex:
  containerSecurityContext:
    runAsGroup: 1000

Group got removed from this one.

server:
  containerSecurityContext:
    runAsUser: 1000
    runAsGroup: 1000

User/group got removed from this one.

repoServer:
  containerSecurityContext:
    runAsUser: 1000
    runAsGroup: 1000

User/group got removed from this one.

I assume these were all accidental since upstream added some defaults, maybe got lost in a update/restore.

added statusdoing label and removed statusreview label

added 1 commit

• 3c40646b - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version