values.yaml

deployment:
  spec:
    # -- replica count
    replicas: 2
    template:
      spec:
        containers:
          image:
            name: virt-operator
            registry: registry.dso.mil/platform-one/big-bang/apps/third-party/kubevirt
            version: v0.54.0
          command:
            port: 8443
            verbosity: 2
          ports:
            metricsPort: 8443
            webhooksPort: 8444
          resources:
            requests:
              cpu: 10m
              memory: 150Mi

# Example of imagePullSecrets settings for private registry access.
# The secrets themselves are created through the bigbang flux integration.
#
#   imagePullSecrets:
#     - name: private-registry
#     - name: repo1-read-creds
imagePullSecrets: []

# Section for configurable workload container options
workloads:
  # https://kubevirt.io/user-guide/operations/installation/#restricting-kubevirt-components-node-placement
  # 
  # You may also need to restrict "workloads" pods(virt-handler)
  # to metal nodes in environments that have a class of metal nodes where
  # nested virt isn't supported. nodeSelector, tolerations
  # and affanity configs are supported for placement.
  nodePlacement: {}

# Section for configurable infra container options
infra:
  # https://kubevirt.io/user-guide/operations/installation/#restricting-kubevirt-components-node-placement
  # 
  # You may want to restrict "infra" pods(virt-controller, virt-api) to just
  # controller nodes. nodeSelector, tolerations and affanity configs are
  # supported for placement.
  nodePlacement: {}

# Software Emulation
#
# docs:
#  - https://github.com/kubevirt/kubevirt/blob/main/docs/software-emulation.md
#  - https://kubevirt.io/user-guide/operations/installation/#installing-kubevirt-on-kubernetes
#
# Many providers do not support nested virtualization with VMs and will fail
# without kubernetes metal worker nodes. Set this to 'true' to enable full
# hardware emulation with qemu. This should not be used in production as
# performance can be dropped by 80% if not using KVM with VT-X or AMD-V CPU
# features.
#
# Even though the docs in the link above say that it will fall back to KVM
# if useEmulation is set, do NOT trust it. We saw that it was still using
# full hardware emulation on metal nodes during tests with this set to 'true'.
useEmulation: false