_defaults.yml

# This file can be used to override default
# role values. This is useful for "downstream"
# packaging and opinionated releases.
#
# This file can be left empty to use the latest and greatest versions of all containers.
# Or it can contain the tags (~= versions) of the containers to install if there is a known combination you want.
# In case you really know what you are doing it is also possible to override the container names here.
# every other package/role specific value should sit in `roles/*/defaults/main.yml`.
#
# A notable exception are common templates, on which we use a two-steps approach to allow the
# users to easily override the installed version. Templates need to be special.
#
# When possible, the 'version' value in the CRs should take precedence over the defaults value.
# The authoritative sources are, in decreasing priority order
# 1. spec.version in the CRs (set by users)
# 2. the *_TAG environment veriable (set by HCO)
# 3. the builtin defaults (set by devs/operator)
# 4. the per-role defaults, which is the last-resort value. Use a low-maintenance, usually working,
#    easy to spot value. 'latest' is a good value here - probably the only case where we should use it.
#
# Any version, or default, should not be set more than once in a place in the source tree.

kubevirt_node_labeller_tag: "{{ lookup('env','NODE_LABELLER_TAG')| default('v0.2.0', true) }}"
kvm_info_nfd_plugin_tag: "{{ lookup('env','KVM_INFO_TAG')| default('v0.5.8', true) }}"
kubevirt_cpu_nfd_plugin_tag: "{{ lookup('env','CPU_PLUGIN_TAG')| default('v0.1.1', true) }}"
virt_launcher_tag: "{{ lookup('env','VIRT_LAUNCHER_TAG')| default('v0.21.0', true) }}"
validator_tag: "{{ lookup('env','VALIDATOR_TAG')| default('v0.7.0', true) }}"
image_name_prefix: "{{ lookup('env','IMAGE_NAME_PREFIX')| default('', true) }}"
templates_version: v0.12.4
operator_version: "{{ lookup('env', 'OPERATOR_VERSION') }}"
os_images_namespace: "kubevirt-os-images"