Set TCP_TARGETS VIP for CAPO workload clusters (!7846) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

On CAPO workload clusters, the Goldpinger TCP_TARGETS environment variable was empty because {{ .Values.cluster_virtual_ip }} is not populated for this setup. This meant Goldpinger was not monitoring the cluster VIP via TCP. Changes: Heat Stack output — Added a new output goldpinger_tcp_targets in the capo-cluster-resources Heat Stack, which produces the cluster VIP in the format IP:6443 using a str_replace on the already-computed VIP address.

sylva-units values — Added a valuesFrom entry for the Goldpinger unit that reads goldpinger_tcp_targets from the capo-cluster-resources ConfigMap and injects it directly into extraEnv[0].value (the TCP_TARGETS env var) via targetPath: extraEnv[0].value. The entry is marked as optional for non-CAPO setups, where cluster_virtual_ip is already populated and the existing value fallback applies.

Closes #4037 (closed)

Test coverage

# flux debug hr goldpinger -n rke2-andra --show-values
extraEnv:
- name: TCP_TARGETS
  value: 192.168.16.139:6443
- name: HTTP_TARGETS
  value: http://goldpinger.goldpinger.svc.cluster.local:8081
ingress:
  className: nginx
  enabled: true
  hosts:
  - host: goldpinger.rke2-andra.wclusters.sylva
    paths:
    - path: /
      pathType: Prefix
  tls:
  - hosts:
    - goldpinger.rke2-andra.wclusters.sylva
    secretName: goldpinger-tls
nodeSelector: {}
rbac:
  create: true
service:
  type: ClusterIP
serviceMonitor:
  enabled: ""
tolerations: []

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

Set TCP_TARGETS VIP for CAPO workload clusters

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports