Assigned
Status Update
No update yet.
Comments
di...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
le...@gmail.com
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
Description
What you would like to accomplish:
Implement loop logic of assigning reserved IPs on instances.
How this might work:
Current API:
"networkInterfaces": [
{
"accessConfigs": [
{
"kind": "compute#accessConfig",
"name": "external-nat",
"natIP": "xx.xx.x.x",
Suggestion:
"networkInterfaces": [
{
"accessConfigs": [
{
"kind": "compute#accessConfig",
"name": "external-nat",
"natIP": "my-reverved-ip-name",
If applicable, reasons why alternative solutions are not sufficient:
Not easy to implement 1 step run logic and have to execute the deployment in two steps.
1. Reserve the IPs and create a reserved iP list.
2. Import the IPs list and iterate it assigning the appropriate IP.
Other information (workarounds you have tried, documentation consulted, etc):
Rest API Calls
Deployment Manager documentation and examples.
k8s is doing is able to use Annotations for Ingress GCP Reserved IP assignment by name