Day 55: The Volume Hides nginx's Log Links, and Every Azure Subnet Gives Up Five Addresses
Day 55 of DevOps, Day 5 of Azure. In both tasks today, the interesting part was something that was already there before I wrote a line. The nginx image had already decided where its logs go, and the sidecar task only works because a volume quietly overrides that decision. And every Azure subnet has five addresses taken before anything is deployed into it. One Kubernetes task, one Azure task. Run…
Day 55 of DevOps and Day 5 of Azure saw two tasks: one involved running a sidecar container that monitored nginx logs, while the other created a virtual network with predefined address ranges. The sidecar container read nginx's logs using an emptyDir volume, which hid nginx's own log output and allowed the sidecar to capture them.
Azure subnets start with five addresses pre-allocated, reducing the number of usable addresses by five. In the Azure task, a VNet named nautilus-vnet was created with a fixed address range of 192.168.0.0/24, leaving 251 usable addresses. The smallest subnet supported by Azure is a /29, which leaves only 3 usable addresses. Azure services often require their own subnets, such as GatewaySubnet, AzureFirewallSubnet, and AzureBastionSubnet, with minimum sizes ranging from /27 to /26.
These address restrictions highlight the importance of planning subnet sizes carefully when setting up Azure networks.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
