VNET IP variables do not take from user env file
Opened this issue · 4 comments
The User custom VNET address space and subnets variables do not apply to the created VNET resource. The AKS pods get it however. This results in an unusable environment. I suggest forcing the user to have a VNET pre allocated for this instead of creating one in the bicep deployment
If I understand this correctly, the user wants to re-use the existing VNET, but doesn't want a new one to be created as part of the TCP to BLOB deployment. If this is the case, then the optional variables under this section of readme can help. If this is something different, we can discuss further.
I did not have an existing VNET. I wanted the script to create a VNET with the option overrides for these parameters by specifying them in my environments file but it got ignored and the VNET created were the default options shown in the readme.
AKS_VNET_ADDR_PREFIX
AKS_VNET_SUBNET_ADDR_PREFIX
LB_IP
AKS_POD_SUBNET_ADDR_PREFIX
AKS_ORBITAL_SUBNET_ADDR_PREFIX
I did not have an existing VNET. I wanted the script to create a VNET with the option overrides for these parameters by specifying them in my environments file but it got ignored and the VNET created were the default options shown in the readme.
AKS_VNET_ADDR_PREFIX AKS_VNET_SUBNET_ADDR_PREFIX LB_IP AKS_POD_SUBNET_ADDR_PREFIX AKS_ORBITAL_SUBNET_ADDR_PREFIX
So despite these parameters were supplied with custom values, the deployment still creates them with default values. Ok, that is interesting. I'll test this and get back to you.