From de3a4abe51fe393a08540d8a6dad4e69e5370780 Mon Sep 17 00:00:00 2001 From: yaroslavborbat Date: Thu, 5 Dec 2024 12:32:01 +0300 Subject: [PATCH] fix Signed-off-by: yaroslavborbat --- ...ed.patch => 025-auto-migrate-if-nodeplacement-changed.patch} | 0 images/virt-artifact/patches/README.md | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename images/virt-artifact/patches/{024-auto-migrate-if-nodeplacement-changed.patch => 025-auto-migrate-if-nodeplacement-changed.patch} (100%) diff --git a/images/virt-artifact/patches/024-auto-migrate-if-nodeplacement-changed.patch b/images/virt-artifact/patches/025-auto-migrate-if-nodeplacement-changed.patch similarity index 100% rename from images/virt-artifact/patches/024-auto-migrate-if-nodeplacement-changed.patch rename to images/virt-artifact/patches/025-auto-migrate-if-nodeplacement-changed.patch diff --git a/images/virt-artifact/patches/README.md b/images/virt-artifact/patches/README.md index c599721c6..d60bb6e76 100644 --- a/images/virt-artifact/patches/README.md +++ b/images/virt-artifact/patches/README.md @@ -84,7 +84,7 @@ Unsuccessful migrations may leave a lot of Pods. These huge lists reduce perform Replace the expressions for the ValidatingAdmissionPolicy kubevirt-node-restriction-policy. This is necessary because of the kube-api-rewriter that changes the labels. -#### `024-auto-migrate-if-nodeplacement-changed.patch` +#### `025-auto-migrate-if-nodeplacement-changed.patch` Start the migration if the nodeSelector or affinity has changed. How does it work?