googlecompute: allow to specify a private ip

[karmab]

Adding the ability to specify network_ip to force a private ip in the image

[rickard-von-essen]

Could you write a quick description on when this would be useful.

[karmab]

@rickard-von-essen the use case is to create an image with a known ip, so that we can later on deploy instances with this same ip.
this is for instance needed when creating a kubernetes image (which will create a kube context with the corresponding ip, and also rely on a non changing hostname)

[rickard-von-essen]

That won't work. The instance launched from the resulting image will not necessarily have the same IP.

[karmab]

indeed, but in my process i force this same ip when instanciating El El mié, 6 jun 2018 a las 21:27, Rickard von Essen < notifications@github.com> escribió:

That won't work. The instance launched from the resulting image will not necessarily have the same IP. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6350 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABwVAw26tOxDeKA1VC4z6PQ_WvZbPpQTks5t6C05gaJpZM4UczVW> .

-- Karim,

[SwampDragons]

This area is definitely not my strong suit, but I don't understand why, if you're forcing the IP when instantiating the instance, you need this to be an option in Packer.

[rickard-von-essen]

IMHO I don't see any reason this should be supported.

[SwampDragons]

Yeah... the use case is still somewhat unclear to me, and this sounds like something that needs to happen in the Kubernetes work instead of within Packer. I'm going to close for now because I am struggling to understand why this change is really needed.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.