Description
In oneKS, if a user instantiates a Kubernetes cluster with a non-owner network, the virtual router creation process fails because the user for the network is needed (two different users can have a network with the same name)
Use case
If a virtual network wants to be used to create kubernetes clusters by multiple users, only the owner of that network will be able to use it. A workaround is reserving a number of IPs on that network and changing the owner of the reservation to the required user.
Interface Changes
In theory, no change should be needed: the VNET should be identified by its ID instead of its name. Being able to set up additional NIC parameters for the virtual router may be a good idea, though.
Additional Context
Ask for more context if needed
Progress Status
Description
In oneKS, if a user instantiates a Kubernetes cluster with a non-owner network, the virtual router creation process fails because the user for the network is needed (two different users can have a network with the same name)
Use case
If a virtual network wants to be used to create kubernetes clusters by multiple users, only the owner of that network will be able to use it. A workaround is reserving a number of IPs on that network and changing the owner of the reservation to the required user.
Interface Changes
In theory, no change should be needed: the VNET should be identified by its ID instead of its name. Being able to set up additional NIC parameters for the virtual router may be a good idea, though.
Additional Context
Ask for more context if needed
Progress Status