Fix IP addressing range issues

This commit is contained in:
Jeroen Vijgen
2026-03-27 23:07:00 +02:00
committed by GitHub
parent a119b970e8
commit ed05c22732
6 changed files with 6 additions and 6 deletions
+1 -1
View File
@@ -61,7 +61,7 @@ You will get 253 usable host addresses per network. This network is mainly for c
For connecting pods to each other (For example: Postgres -> Project <- Redis ) I use the following IP range and Subnet:
- 172.17.0.0 - 172.17.0.254
- 172.32.0.0 - 172.32.0.254
- 255.255.255.248 (/29)
You get 6 usable host addresses per internal network, to find the usable addresses you can check [here](https://www.calculator.net/ip-subnet-calculator.html?cclass=b&csubnet=29&cip=172.16.0.0&ctype=ipv4&x=Calculate).
@@ -46,7 +46,7 @@ module "wings_network" {
name = "pelican-wings"
driver = "bridge"
attachable = true
subnet = "172.18.0.0/16"
subnet = "172.64.0.0/16"
options = {
"com.docker.network.bridge.name" = "pelican-wings"
}
@@ -80,7 +80,7 @@ resource "local_file" "authentik_config_file" {
module "authentik_network" {
source = "../../01-networking/network-service"
name = "authentik-network"
subnet = "172.17.0.0/29"
subnet = "172.32.0.0/29"
driver = "bridge"
options = {
"isolate" : false
@@ -53,7 +53,7 @@ locals {
module "coder_network" {
source = "../../01-networking/network-service"
name = "coder-network"
subnet = "172.17.0.16/29"
subnet = "172.32.0.16/29"
driver = "bridge"
options = {
"isolate" : false
@@ -85,7 +85,7 @@ locals {
module "penpot_network" {
source = "../../01-networking/network-service"
name = "penpot-network"
subnet = "172.17.0.32/29"
subnet = "172.32.0.32/29"
driver = "bridge"
options = {
"isolate" : false
@@ -62,7 +62,7 @@ locals {
module "tandoor_network" {
source = "../../01-networking/network-service"
name = "tandoor-network"
subnet = "172.17.0.24/29"
subnet = "172.32.0.24/29"
driver = "bridge"
options = {
"isolate" : false