minor: Add ingressClassName to Vault definition and remove deprecated annotation (!7878) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

While working on #3329, I noticed that the Vault CR that we are defining in https://gitlab.com/sylva-projects/sylva-core/-/blob/main/kustomize-units/vault/vault.yaml?ref_type=heads, is missing the ingress Class. It looks like this is supported by the CRD:

k explain vault.spec.ingress.spec.ingressClassName
GROUP:      vault.banzaicloud.com
KIND:       Vault
VERSION:    v1alpha1

FIELD: ingressClassName <string>


DESCRIPTION:
    <empty>

This MR is adding this field in to the Vault definition file. It is also removing the deprecated ingress annotation (https://kubernetes.io/docs/concepts/services-networking/ingress/#deprecated-annotation)

Test coverage

Tested in my dev environment and the ingressClass is getting updated accordingly.

 k get ingress -n vault
NAME    CLASS                          HOSTS         ADDRESS          PORTS     AGE
vault   rke2-ingress-nginx-migration   vault.sylva   192.168.19.239   80, 443   13h

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 May 20, 2026 by Dragos Gerea

minor: Add ingressClassName to Vault definition and remove deprecated annotation

What does this MR do and why?

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports