feat(ibmcloud): remove public gateway from VPC network module — use FIP-only for outbound

オープン
#936 コメント 4 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 4 日以内に返信

@adrianriobo がすでに取り組んでいます。

2026年10月16日 から。

評価

この issue はまだ評価されていません。

説明

provider/IBMCLOUD wontfix

Background

Every IBM Cloud VPC target that uses network.New() (kind, snc, ibm-z, ibm-gaudi) provisions two outbound internet paths:

  1. Public Gateway — subnet-level; all instances in the subnet can reach the internet immediately from first boot.
  2. Floating IP — instance-level 1:1 NAT; provides both inbound SSH/API access and outbound internet once attached.

The floating IP alone is sufficient for outbound connectivity. Once it is associated with an instance's NIC, the instance uses the FIP's public address for all outbound traffic — no gateway needed.

Why the gateway exists today

The Pulumi resource graph attaches the floating IP after the instance is created (it needs the NIC ID):

network.New() → FIP reserved (not yet attached)
↓
NewIsInstance() → VM boots, cloud-init starts
↓
NewIsInstanceNetworkInterfaceFloatingIp() → FIP attached

There is a window between "instance running" and "FIP associated" during which cloud-init runs apt-get update and downloads the kind binary and node image. Without the public gateway that window has no outbound internet path and cloud-init fails.

The gateway is attached to the subnet before the instance exists, so it covers that window reliably.

Opportunity

The IBM Cloud VPC REST API accepts primary_network_interface.floating_ips[] during instance creation, allowing the FIP to be associated atomically — the instance would boot with the FIP already wired, eliminating the race window entirely.

If the Pulumi IBM Cloud provider exposed this field on IsInstancePrimaryNetworkInterfaceArgs, we could:

  • Pass the pre-created FIP ID at instance creation time
  • Drop the separate IsInstanceNetworkInterfaceFloatingIp resource
  • Remove the public gateway and its subnet attachment entirely

Current blocker

IsInstancePrimaryNetworkInterfaceArgs in pulumi-ibmcloud v0.0.16 does not include a FloatingIps field:

type IsInstancePrimaryNetworkInterfaceArgs struct {
    AllowIpSpoofing    pulumi.BoolPtrInput
    Name               pulumi.StringPtrInput
    PrimaryIp          IsInstancePrimaryNetworkInterfacePrimaryIpPtrInput
    SecurityGroups     pulumi.StringArrayInput
    Subnet             pulumi.StringInput
    // FloatingIps missing — IBM Cloud API supports this
}

Cost and simplification benefit

  • One fewer VPC resource per stack (public gateway + subnet attachment): reduces IBM Cloud VPC resource quota consumption and simplifies teardown.
  • Public gateways themselves are not charged hourly by IBM Cloud, but data egress through them is billed at the same rate as through a FIP. Net cost saving is minimal but quota consumption drops.
  • The main gain is architectural simplicity: a single outbound path (the FIP) instead of two overlapping ones.

Proposed path

  1. Open an issue or PR against mapt-oss/pulumi-ibmcloud to expose FloatingIps []string on IsInstancePrimaryNetworkInterfaceArgs.
  2. Once the SDK is updated, refactor network.New() to:
    • Accept the pre-created FIP ID
    • Pass it in PrimaryNetworkInterface.FloatingIps
    • Remove NewIsPublicGateway and NewIsSubnetPublicGatewayAttachment
    • Remove the separate NewIsInstanceNetworkInterfaceFloatingIp call from each action
主要言語
Go
スター
25
フォーク
41
平均マージ
5日 3時間
マージ済み PR(30日)
16

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

redhat-developer/mapt のほかの issue

redhat-developer/mapt の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。