Skip to main content

VMO Pack Parameters

The parameters on this page come from the Virtual Machine Orchestrator (VMO) pack base values and are not changed by any Deployment Mode or authentication selection. Override them directly in the pack YAML when needed. Refer to the Virtual Machine Orchestrator pack documentation for the full list of parameters that the pack exposes.

warning

We recommend using the pack defaults. Default settings provide best practices for your clusters. Changing the default settings can introduce misconfigurations. Carefully review the changes you make to a pack.

Values Paths​

Unless stated otherwise, the parameters on this page are relative to the following values root.

charts:
virtual-machine-orchestrator:
vmo-manager:

For example, logging.level refers to charts.virtual-machine-orchestrator.vmo-manager.logging.level.

Deployment​

ParameterDefaultDescription
deployment.replicaCount1Set to 3 for high availability on multi-node control planes. Anti-affinity and the pod disruption budget turn on automatically when the count is greater than 1.
service.port8080
oidc.clientIdk8s-oidc
oidc.scopes"", which resolves to openid,profile,email,groupsThe groups scope is always requested, even if you omit it from this list.
oidc.k8sUsernameClaimemailMust match the Kubernetes API server --oidc-username-claim flag. Palette clusters use email.
oidc.k8sNotFederatedfalseSet to true when the Kubernetes API server is not federated with the same OIDC issuer as VMO. Refer to Configure Non-Federated Kubernetes API Servers for the behavior it changes and the security trade-off.
platform.cdiProxyUrlhttps://cdi-uploadproxy.cdi.svc.cluster.local
platform.caFile/etc/ssl/custom/ca.crt
identity.keycloakAdminClientIdvmo-admin
logging.levelinfoSet to debug to troubleshoot bootstrap, leader election, and identity seeding.
secrets.createtrueGenerates the session key on first install and preserves it across upgrades.
features.guestAgentAutoInstalltrueInjects the QEMU guest agent through cloud-init.
goldenImagesNamespacevmo-golden-images

TLS and Ingress​

ParameterBase DefaultAfter Proxied or Direct
tls.enabledfalsetrue
tls.certManager.enabledfalsetrue
tls.certManager.selfSignedfalsetrue
tls.certManager.issuerNameplatform-ca-issuerIgnored when selfSigned is true
tls.certManager.duration8760h, or one yearUnchanged
tls.certManager.renewBefore720h, or 30 daysUnchanged
ingressRoute.enabledtruefalse
ingress.enabledfalseUnchanged

Audit and Metrics​

ParameterDefaultDescription
audit.retentionDays30Set to 0 to disable the cleanup CronJob. Audit events then accumulate without limit.
audit.cleanupSchedule0 0 * * *Runs daily at midnight UTC. Ignored when audit.retentionDays is 0.
metrics.externalMetricsEnabledfalseEnable to query an external PromQL backend, such as Victoria Metrics or Thanos, for long ranges.
metrics.retentionDays30Internal metric retention.
metrics.ringBufferRetention30mIn-memory buffer used when the external backend is unavailable.

Components​

Every component in the pack can be turned on or off independently. This is useful when a component is already installed on the cluster or is managed by another team.

ComponentParameterDefault
VMO Managervmo-manager.enabledtrue
VMO Manager CRDsvmo-manager-crds.enabledtrue
KubeVirtkubevirt.enabledtrue
Containerized Data Importercdi.enabledtrue
Multusmultus.enabledtrue
Snapshot controllersnapshot-controller.enabledtrue
Deschedulerdescheduler.enabledtrue
Node agent DaemonSetvmo-manager.nodeAgent.enabledtrue
Cilium NetworkPolicyvmo-manager.networkPolicy.enabledfalse
VLAN filtering DaemonSetvlanFiltering.enabledfalse
Post-delete cleanup jobcleanup.enabledtrue

The parameters in this table are relative to charts.virtual-machine-orchestrator, not to the vmo-manager sub-chart.

Enable vmo-manager.networkPolicy.enabled only on clusters that use Cilium as the CNI.

Next Steps​

Refer to Create a VMO Profile to apply these parameters in an add-on cluster profile.