Fix harbor SSO test in case of upgrade (!8215) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Multiple issues were noticed during Harbor SSO tests (see: #4211 (closed)) within our upgrade pipeline scenarios. I attempted to replicate these behaviors locally and identified several key problems:

Incorrect resource IDs in ClientScopes/ClientDefaultScopes

These resources do not reference the correct client ID. Instead, they attempt to use outdated ID that have already been deleted. This issue appears from a race condition between the deletion of legacy resources and the recreation of clients managed via Crossplane or because we are using same name for cliendId.

- lastTransitionTime: "2026-06-08T10:37:28Z"
    message: 'create failed: async create failed: failed to create the resource: [{0
      validation error: client with id 87f5bc69-fb01-4ba1-bf50-931b4589a9b6 does not
      exist  []}]'
    observedGeneration: 3
    reason: ReconcileError
    status: "False"
    type: Synced

apiVersion: legacy.k8s.keycloak.org/v1alpha1
kind: KeycloakClient
metadata:
  creationTimestamp: "2026-06-08T09:00:49Z"
  finalizers:
  - client.cleanup
  generation: 2
  labels:
    kustomize.toolkit.fluxcd.io/name: keycloak-resources
    kustomize.toolkit.fluxcd.io/namespace: sylva-system
    realm1: sylva
  name: harbor-client
  namespace: keycloak
  resourceVersion: "38741"
  uid: fc452801-d7c7-4954-97d7-9e39ae007d29
spec:
  client:
    clientId: harbor
    id: 87f5bc69-fb01-4ba1-bf50-931b4589a9b6<= old id

ClientSecret atribute is empty or not updated

The clientSecret field is often empty or not propagated correctly. Although we manage this via an external secret operator, there are cases where the field remains empty or isn't updated during transitions from legacy to Crossplane solutions.

 "oidc_client_id": "harbor",
 "oidc_client_secret": "", <=  empty
 "oidc_scope": "openid,email,profile,offline_access",

After updating the client and obtaining a new token, the application does not automatically reload the updated configuration. Currently, there is no mechanism in place to trigger a reload, which results in outdated settings being used.

The scope of this MR is to provide a solution for each problem presented above:

Change clientId name to harbor-client and in the same time renamed resources related to harbor sso integration in order to avoid misconfiguration. On the other part, similar to the strategy implemented in !7715 (merged), we should enable policy for all crospplane resources.
Reduce the refreshInterval in the ExternalSecret configuration to 15m. This shorter interval will help to fill the gap between client creation and secret update.
Move creation of external secret under harbor-oidc unit and keep all the resources related to oidc integration in one place and add addional healthchecks.

Closes #4211 (closed).

Test coverage

Upgrade: https://gitlab.com/sylva-projects/sylva-core/-/jobs/14976765791#L137

Fresh install: https://gitlab.com/sylva-projects/sylva-core/-/jobs/14972879263

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Jun 23, 2026 by Bogdan Antohe

Fix harbor SSO test in case of upgrade

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports