Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipv6AccessConfigs.externalIpv6 is ignored #2960

Open
ohardy opened this issue Feb 8, 2025 · 0 comments
Open

ipv6AccessConfigs.externalIpv6 is ignored #2960

ohardy opened this issue Feb 8, 2025 · 0 comments
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team

Comments

@ohardy
Copy link

ohardy commented Feb 8, 2025

Describe what happened

Hello,

ipv6AccessConfigs.externalIpv6 is ignored in compute.Instance call

I create an IP address

const publicIpV6 = new compute.Address('test', {
    addressType: 'EXTERNAL',
    name: 'test',
    subnetwork,
    ipVersion: 'IPV6',
    ipv6EndpointType: 'VM',
  });

And I use it in compute.Instance creation

networkInterfaces: [
      {
        accessConfigs: [
          {
            natIp: publicIp.address,
          },
        ],
        ipv6AccessConfigs: [
          {
            name: publicIpV6.name,
            externalIpv6: publicIpV6.address,
            networkTier: 'PREMIUM',
          },
        ],
        networkIp: staticIp.address,
        subnetwork,
        stackType: 'IPV4_IPV6',
      },
    ],

GCP don't use the provided IP address but use an ephemeral one. If I go in GCP console, I can edit the VM and select this reserved IP address.

Any idea why pulumi just ignore it ?

Thanks in advance,
Olivier

Sample program

const publicIpV6 = new compute.Address('test', {
    addressType: 'EXTERNAL',
    name: 'test',
    subnetwork,
    ipVersion: 'IPV6',
    ipv6EndpointType: 'VM',
  });

And I use it in compute.Instance creation

networkInterfaces: [
      {
        accessConfigs: [
          {
            natIp: publicIp.address,
          },
        ],
        ipv6AccessConfigs: [
          {
            name: publicIpV6.name,
            externalIpv6: publicIpV6.address,
            networkTier: 'PREMIUM',
          },
        ],
        networkIp: staticIp.address,
        subnetwork,
        stackType: 'IPV4_IPV6',
      },
    ],

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

CLI
Version 3.148.0
Go Version go1.23.5
Go Compiler gc

Plugins
KIND NAME VERSION
language nodejs 3.148.0-dev.0

Host
OS darwin
Version 15.3
Arch arm64

This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v23.7.0'

Current Stack: ----/----/global

TYPE URN
pulumi:pulumi:Stack urn:pulumi:global::gcp-bastion::pulumi:pulumi:Stack::gcp-bastion-global
pulumi:providers:pulumi urn:pulumi:global::gcp-bastion::pulumi:providers:pulumi::default
pulumi:providers:gcp urn:pulumi:global::gcp-bastion::pulumi:providers:gcp::default_8_18_0
gcp:compute/disk:Disk urn:pulumi:global::gcp-bastion::gcp:compute/disk:Disk::bastion-wireguard
gcp:compute/address:Address urn:pulumi:global::gcp-bastion::gcp:compute/address:Address::bastion-ipv4
pulumi:pulumi:StackReference urn:pulumi:global::gcp-bastion::pulumi:pulumi:StackReference::----/----/host
gcp:compute/address:Address urn:pulumi:global::gcp-bastion::gcp:compute/address:Address::bastion
gcp:compute/address:Address urn:pulumi:global::gcp-bastion::gcp:compute/address:Address::bastion-ipv6
gcp:compute/instance:Instance urn:pulumi:global::gcp-bastion::gcp:compute/instance:Instance::bastion

Found no pending operations associated with -----/global

Backend
Name pulumi.com
URL https://app.pulumi.com/----
User ----
Organizations ---, ----
Token type personal

Pulumi locates its logs in /var/folders/g4/w864n44d0jx2225wqt31h4mr0000gn/T/ by default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@ohardy ohardy added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Feb 8, 2025
@ohardy ohardy changed the title ipv6AccessConfigs.externalIpv6 ipv6AccessConfigs.externalIpv6 is ignored Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team
Projects
None yet
Development

No branches or pull requests

1 participant