Assigned
Status Update
No update yet.
Comments
da...@schweikert.ch
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
kn...@google.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
I am thinking that to make the full setup of our productive environment more robust and flexible, we should use multiple deployments. For example one deployment for setting up networking and the external IP, and a separate deployment for a kubernetes cluster.
One problem that I have with that approach, is that I have to put in the configuration some parameters that could be found in the resource data from the other deployment. For example the external IP address: I'd like to get that automatically when setting up the kubernetes cluster, without needing me to hardcode the IP address created in the networking deployment, in the kubernetes deployment configuration.
What would be really cool, is the possibility to reference data from other deployments. Something like:
$(ref.network-deployment/external-ip.address)