docs(infrastructure): describe the outbound-only public IP

[lorenzocorallo]

Updates the infrastructure docs for the egress change: k3s01 reaches the Internet through an outbound-only public IP on its NIC instead of a NAT Gateway, which saves about USD 33/month.

• Removes "no public IP" and "NAT Gateway" from the setup, Terraform, K3s node and cloud infrastructure pages.
• Notes that the host firewall accepts SSH only from private ranges (WARP sessions arrive from the cloudflared pods).

Merge after PoliNetworkOrg/terraform#90, the cutover, is applied.

Related: PoliNetworkOrg/polinetwork-cd#24, PoliNetworkOrg/terraform#89 → #90 → #91.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: b889064f-daa8-403d-b35b-ec1c0ffc6542

---

---

📥 Commits

Reviewing files that changed from the base of the PR and between 26d4e95 and 122065f.

---

---

📒 Files selected for processing (4)

• content/docs/infrastructure/getting-started/cloud-infrastructure/index.mdx
• content/docs/infrastructure/getting-started/cloud-infrastructure/k3s-node.mdx
• content/docs/infrastructure/getting-started/cloud-infrastructure/terraform.mdx
• content/docs/infrastructure/getting-started/setup.mdx

---

---

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

---

---

Walkthrough

The infrastructure guides now describe the K3s VM public IP as outbound-only instead of documenting a NAT Gateway or no public IP. The node access guidance also clarifies the host firewall’s SSH source ranges.

Changes

K3s network documentation

Layer / File(s)	Summary
Outbound IP description content/docs/infrastructure/getting-started/cloud-infrastructure/index.mdx, content/docs/infrastructure/getting-started/cloud-infrastructure/terraform.mdx	The guides describe outbound traffic as using the VM public IP instead of a NAT Gateway.
Node IP and access description content/docs/infrastructure/getting-started/cloud-infrastructure/k3s-node.mdx, content/docs/infrastructure/getting-started/setup.mdx	The guides describe the public IP as outbound-only. The node guardrails specify that the host firewall allows SSH from private ranges. The private address and NSG inbound-denial description remain.

Priority: ⬇️ Low

Change: Other

Merge Risk: 🟡 Moderate · up to 12206

Confirm the production cutover before merging these guides. PR #90 remains open and reports no deployments; without confirmation, readers may receive a premature description of the network.

Pre-merge checks | 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly and concisely describes the main documentation change: documenting the outbound-only public IP.

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Pages Preview
Preview removed because the pull request was closed.
2026-10-10 20:33:59 +0000