Azure/azure-orbital-integration

TCP to BLOB - Pass IP range env variables to bicep

Opened this issue · 0 comments

micholas commented

TCP to BLOB initially used only shell scripts for deployment. At the time the IP ranges were able to be set via environment variables. It appears these were never leveraged within bicep which is currently used.

  • LB_IP
  • AKS_VNET_ADDR_PREFIX
  • AKS_VNET_SUBNET_ADDR_PREFIX LB_IP
  • AKS_POD_SUBNET_ADDR_PREFIX
  • AKS_ORBITAL_SUBNET_ADDR_PREFIX

These defaults are assigned in this file:
https://github.com/Azure/azure-orbital-integration/blob/main/tcp-to-blob/deploy/env-defaults.sh#L14

And should be used in this one:
https://github.com/Azure/azure-orbital-integration/blob/main/tcp-to-blob/deploy/bicep/aks.bicep#L32

We will need to create a param in aks.bicep for each of the environment variables above and pass the environment variables to set these params when the bicep template is deployed:
https://github.com/Azure/azure-orbital-integration/blob/main/tcp-to-blob/deploy/bicep/deploy-core.sh#L34