I was minutes away from filing this as a new bug report myself, as it seemed to be an unintentional template file edit that breaks ArgoCD SSO integration with keycloak when upgrading from a previous version of Big Bang. We found this upgrading from 2.16.0 to 2.21.1.
Impact:
Trying to SSO login via keycloak to a SSO enabled ArgoCD UI throws an error message in the browser: "failed to get token: oauth2: "unauthorized_client" "Invalid client or Invalid client credentials""
I would vote to restore the .Values.sso.enabled conditional in the "if" check for the argocd-secret.yaml template, rather then providing any new way to get the "oidc.keycloak.clientSecret:" name/value pair written to the secret manifest. This seems reasonable since the {{- if .Values.sso.enabled }} section still exists at the bottom of the template file.