No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

as far as I can see, this is how the actual code calculates the subnets

It seems that in the for cycle for the isolated, the last IP is not taken in account for the next AZs base ip

Further updates:
• we found that the issue with the `v1.0.0` happens because we defined the Private subnet with `cidrMask: 18` 
• this happens because, with 3 AZs, the base IP are divided using the `/18` mask in 4 (leaving a single `/18` free) and the subnetSpecs ip calculations applied starting from the baseIp, so `/18` + `/20` + `/22` are overlapping, which wasn't happening before the upgrade.
