What happened:
Kubemacpool allows users to define a static macpool range. There is no capability to generate MAC address range by hashing with any unique ID like k8s Cluster ID/name/UUID. In vendor provided solutions like VMWare hash vsphere cluster ID to generate the MAC address range for VMs
What you expected to happen:
Kubevirtmacpool operator will dynamically generate the mac address pool range by hashing a unique ID/UUID/Clustername of the k9s cluster.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
It would be great to have an option to generate Unique MAC address ranges for a k8s cluster by hashing a unique ID/name/UUID/domain name of a cluster
What happened: Kubemacpool allows users to define a static macpool range. There is no capability to generate MAC address range by hashing with any unique ID like k8s Cluster ID/name/UUID. In vendor provided solutions like VMWare hash vsphere cluster ID to generate the MAC address range for VMs
What you expected to happen: Kubevirtmacpool operator will dynamically generate the mac address pool range by hashing a unique ID/UUID/Clustername of the k9s cluster. How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
It would be great to have an option to generate Unique MAC address ranges for a k8s cluster by hashing a unique ID/name/UUID/domain name of a cluster
Environment: