[release-1.7] Fix NeuVector SSO in case of upgrade (!8668) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

The initial issue was discovered on the upgrade from release 1.6 to 1.7.

We have observed recurring issue during NeuVector SSO tests (see https://gitlab.com/sylva-projects/sylva-core/-/jobs/15508702439#L153) within our upgrade pipeline scenarios. I attempted to replicate these behaviors locally and identified the next problem:

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.

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

Change clientId name to neuvector-client in order to avoid misconfiguration. On the other part, similar to the strategy implemented in !7715 (merged) (merged), we should enable policy for all crospplane resources.
Add the refreshInterval in the ExternalSecret configuration with the value of 15m. This short interval will help to fill the gap between client creation and secret update.
Add synchronize: true in kyverno-neuvector-policies wherew the secret neuvector-init is generated, because even if the components of the secret are updated, the secret itself needs to be synchronized.
Keep all the resources related to oidc integration in one place.

Closes #4402 (closed)

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 Aug 12, 2026 by Andra-Simona Delicostea

[release-1.7] Fix NeuVector SSO in case of upgrade

What does this MR do and why?

CI configuration

Global config for deployment pipelines

Merge request reports