Per team meeting, we're interested in having the kube-ovn charm "just work" on older AMD64 machines that don't support AVX-512. A couple options come to mind:
1. Check CPU capabilities at deploy time and select the -no-avx512 image if needed
2. Publish our own kube-ovn multi-arch image that uses the -no-avx512 image for amd64
I think option 1 could get complicated as we have to check CPU capabilities across both kubernetes-control-plane and kubernetes-worker applications. I would recommend option 2 as a simpler, safer alternative.
Per team meeting, we're interested in having the kube-ovn charm "just work" on older AMD64 machines that don't support AVX-512. A couple options come to mind:
1. Check CPU capabilities at deploy time and select the -no-avx512 image if needed
2. Publish our own kube-ovn multi-arch image that uses the -no-avx512 image for amd64
I think option 1 could get complicated as we have to check CPU capabilities across both kubernetes- control- plane and kubernetes-worker applications. I would recommend option 2 as a simpler, safer alternative.