Description of problem: For various reasons (security being one), users should be able to specify a TTL for the VMExport objects Version-Release number of selected component (if applicable): CNV 4.12.0 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: No mechanism to specify a TTL Expected results: TTL supported Additional info:
Verified on CNV-v4.12.0-665 Create a VM and stop it: $ oc create -f vm-ocs.yaml virtualmachine.kubevirt.io/vm-cirros-source-ocs created $ oc get vm -A NAMESPACE NAME AGE STATUS READY default vm-cirros-source-ocs 28s Running True $ virtctl stop vm-cirros-source-ocs VM vm-cirros-source-ocs was scheduled to stop Create a token: $ cat token.yaml apiVersion: v1 kind: Secret metadata: name: virt-export-token data: token: bXl0b2tlbg== $ oc create -f token.yaml secret/virt-export-token created Create VMExport with ttlDuration: $ cat vmexport-vm-ttl.yaml apiVersion: export.kubevirt.io/v1alpha1 kind: VirtualMachineExport metadata: name: export-vm-object spec: source: apiGroup: "kubevirt.io" kind: VirtualMachine name: vm-cirros-source-ocs tokenSecretRef: virt-export-token ttlDuration: 2m $ oc create -f vmexport-vm-ttl.yaml virtualmachineexport.export.kubevirt.io/export-vm-object created $ oc get vmexport NAME SOURCEKIND SOURCENAME PHASE export-vm-object VirtualMachine vm-cirros-source-ocs Ready Wait for 2 minutes: $ oc get pods -w NAME READY STATUS RESTARTS AGE virt-export-export-vm-object 1/1 Running 0 78s virt-export-export-vm-object 0/1 Completed 0 2m virt-export-export-vm-object 0/1 Terminating 0 2m virt-export-export-vm-object 0/1 Terminating 0 2m2s virt-export-export-vm-object 0/1 Terminating 0 2m2s virt-export-export-vm-object 0/1 Terminating 0 2m2s $ oc get pods No resources found in default namespace. $ oc get vmexport No resources found in default namespace.
We also need to mention the TTL feature in kubevirt user-guide https://kubevirt.io/user-guide/operations/export_api/#export-api
Thanks @akalenyu for the quick response with the user-guide PR: https://github.com/kubevirt/user-guide/pull/614
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.12.0 Images security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:0408