Reference

Configuration Options

Type: Reference (Information-oriented)

config.yaml

The central configuration file at dp-infra/cloud-vinyl/config.yaml drives the entire deployment.

versions

Field	Type	Required	Description
versions.operator	string	Yes	Cloud-vinyl Helm chart version (matches appVersion)

helmRepo

Field	Type	Required	Description
helmRepo.url	string	Yes	OCI Helm registry URL. Default: oci://ghcr.io/bluedynamics/charts

namespace

Field	Type	Required	Default	Description
namespace	string	Yes	cloud-vinyl-system	Kubernetes namespace for operator

operator

Field	Type	Required	Default	Description
operator.leaderElection	boolean	No	true	Enable leader election for HA
operator.webhook.certManager	boolean	No	true	Use cert-manager for webhook TLS
operator.monitoring.prometheusRules	boolean	No	false	Deploy PrometheusRule with alerts
operator.monitoring.prometheusRuleLabels	map	No	{}	Extra labels on the PrometheusRule (chart additionalLabels, requires cloud-vinyl >= 0.5.1)
operator.monitoring.serviceMonitor	boolean	No	false	Deploy ServiceMonitor for scraping

Note

The kup6s Prometheus selects rules via ruleSelector: {release: kube-prometheus-stack}. A PrometheusRule without that label is created but never loaded. The kup6s config therefore sets prometheusRuleLabels: {release: kube-prometheus-stack} so the alerts evaluate. The systemic alternative — making Prometheus select all rules cluster-wide — is tracked in cdk8s-monitoring#3.

resources

Field	Type	Required	Default	Description
resources.operator.requests.cpu	string	No	25m	CPU request
resources.operator.requests.memory	string	No	128Mi	Memory request
resources.operator.limits.cpu	string	No	100m	CPU limit
resources.operator.limits.memory	string	No	256Mi	Memory limit

Example

versions:
  operator: "0.5.1"

helmRepo:
  url: "oci://ghcr.io/bluedynamics/charts"

namespace: "cloud-vinyl-system"

operator:
  leaderElection: true
  webhook:
    certManager: true
  monitoring:
    prometheusRules: true
    prometheusRuleLabels:
      release: kube-prometheus-stack
    serviceMonitor: true

resources:
  operator:
    requests:
      cpu: "25m"
      memory: "128Mi"
    limits:
      cpu: "100m"
      memory: "256Mi"