[backport-1.7] GitOps: Add proxy via secret in gitrepos (!9353) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Test coverage

crustgather-job-16831569708 ~> k get gitrepository rancher-roles-management-repo -o yaml
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  creationTimestamp: "2026-09-30T10:33:52Z"
  finalizers:
  - finalizers.fluxcd.io
  generation: 1
  labels:
    kustomize.toolkit.fluxcd.io/name: rancher-roles-management-repo
    kustomize.toolkit.fluxcd.io/namespace: sylva-system
    sylva.org/sylva-managed: "true"
  name: rancher-roles-management-repo
  namespace: sylva-system
  resourceVersion: "11942"
  uid: f1143202-e762-4b86-bdf6-48cae99f3024
spec:
  interval: 5m
  proxySecretRef:
    name: rancher-roles-management-repo-git-proxy <= secret proxy name
  ref:
    tag: 1.1.0
  secretRef:
    name: rancher-roles-management-repo-secret-ref
  timeout: 60s
  url: https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/sample-keycloak-users-groups-repo.git
status:
  artifact:
    digest: sha256:eb23478373661775ff8d3f64351bf5423f796115d3266bc2f355f32d75b0c699
    lastUpdateTime: "2026-09-30T10:33:54Z"
    path: gitrepository/sylva-system/rancher-roles-management-repo/e8e63de196179c0db428c5988c5062fd979496c2.tar.gz
    revision: 1.1.0@sha1:e8e63de196179c0db428c5988c5062fd979496c2
    size: 6185
    url: http://source-controller.flux-system.svc.cluster.local./gitrepository/sylva-system/rancher-roles-management-repo/e8e63de196179c0db428c5988c5062fd979496c2.tar.gz
  conditions:
  - lastTransitionTime: "2026-09-30T10:33:54Z"
    message: stored artifact for revision '1.1.0@sha1:e8e63de196179c0db428c5988c5062fd979496c2'
    observedGeneration: 1
    reason: Succeeded
    status: "True"
    type: Ready
  - lastTransitionTime: "2026-09-30T10:33:54Z"
    message: stored artifact for revision '1.1.0@sha1:e8e63de196179c0db428c5988c5062fd979496c2'
    observedGeneration: 1
    reason: Succeeded
    status: "True"
    type: ArtifactInStorage
  observedGeneration: 1

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 Sep 30, 2026 by Bogdan Antohe

[backport-1.7] GitOps: Add proxy via secret in gitrepos

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports