-
Story
-
Resolution: Done
-
Undefined
-
None
-
8
-
False
-
-
False
-
-
-
-
GitOps Scarlet Sprint 17, GitOps Scarlet Sprint 18, GitOps Scarlet Sprint 19
The goal of this story is to deprecate Keycloak within OpenShift GitOps (with the goal of eliminating it in a subsequent release). Keycloak support should still continue to work, but will be listed as deprecated in doc, in code, and in operator logs.
Slack thread for more details: https://redhat-internal.slack.com/archives/C072XEET171/p1749039415795409?thread_ts=1737090625.150739&cid=C072XEET171
Acceptance Criteria:
- Add a deprecation notice to openshift gitops docs indicating keycloak support is being removed.
- Link to the following resources on how to replace it:
- Existing OpenShift GitOps Dex docs
- Configuring Keycloak from Argo CD: https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/keycloak/#keycloak-and-argocd-with-pkce
- Use ArgoCD CR `.spec.oidcConfig` field for SSO configuration.
- Red Hat Build of Keycloak Operator: https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html/operator_guide/installation-
- Include this notice as both a release note, and in Configuring SSO for Argo CD for Keycloak (https://docs.redhat.com/en/documentation/red_hat_openshift_gitops/1.16/html/access_control_and_user_management/configuring-sso-for-argo-cd-using-keycloak).
- Link to the following resources on how to replace it:
- Create a PR in argocd-operator:
- Add comment to keycloak fields that the fields are deprecated, and in a future release will no longer be supported.
- Log a message if keycloak functionality is used
- Otherwise, keycloak functionality will continue to work as expected (e.g. don't no-op yet)
- Merge PR
- No unit/E2E tests needed, I believe.