You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow for a NIC to have multiple IP configurations
Describe the Need:
We operate Kubernetes Clusters on Azure (not AKS) and need to provision NICs with multiple IP configurations (addresses) for Azure-CNI to work. I am unsure if others would find this useful but I imagine there are other examples where a VM would want multiple IP addresses per NIC.
Current Alternative
Currently we test Kubernetes in Test Kitchen with Weave but deploy to Dev/Staging/Prod with Terraform and Azure-CNI. Our Test Kitchen workflows would benefit from using the same CNI.
Can We Help You Implement This?:
Happy to implement this myself and open a PR assuming:
The project feels it would benefit from this feature
The Azure API can handle this without having to summon Cthulhu
The text was updated successfully, but these errors were encountered:
Thanks for opening this @cpressland. I think this would be good functionality to add, and we'd be happy to help you get a PR through; unfortunately I can't answer offhand how well the Azure API would be able to handle it, though I would expect it's a supported use case.
Describe the Enhancement:
Allow for a NIC to have multiple IP configurations
Describe the Need:
We operate Kubernetes Clusters on Azure (not AKS) and need to provision NICs with multiple IP configurations (addresses) for Azure-CNI to work. I am unsure if others would find this useful but I imagine there are other examples where a VM would want multiple IP addresses per NIC.
Current Alternative
Currently we test Kubernetes in Test Kitchen with Weave but deploy to Dev/Staging/Prod with Terraform and Azure-CNI. Our Test Kitchen workflows would benefit from using the same CNI.
Can We Help You Implement This?:
Happy to implement this myself and open a PR assuming:
The text was updated successfully, but these errors were encountered: