K8s-config-connector: Support referencing IP from to-be-created ComputeAddress

[shogomuranushi]

I want to put the value of ComputeAddress in rrdatas of DNSRecordSet.

When I look at the references, it looks like I can't do external references.
Is there any good way?

apiVersion: compute.cnrm.cloud.google.com/v1beta1
kind: ComputeAddress
metadata:
  name: staticip
spec:
  location: global
---
apiVersion: dns.cnrm.cloud.google.com/v1beta1
kind: DNSRecordSet
metadata:
  name: xxx-recorad
spec:
  name: "xxx.example.com."
  type: "A"
  ttl: 300
  managedZoneRef:
    external: managezone
  rrdatas:
  - "8.8.8.8" # <-- I want to put the IP address created with ComputeAddress here.

[AlexBulankou]

@shogomuranushi , thanks for reporting the issue. At this time it is not possible with Config Connector to reference a value of ComputeAddress's IP address dynamically, so you would need to wait until ComputeAddress is created and update rrdatas then.
As part of our larger effort to improve end-to-end provisioning scenarios for IP address we are considering improvements in this area later in 2020; we'll update this thread with more information then.

[snuggie12]

Will this allow for any kind of reference? We want to be able to reference the IP address of a load balancer created by a k8s service. The load balancer's name is randomized so referencing the k8s service's status.loadBalancer.ingress.ip.0 would have the IP I'm looking for.

[thecloudgeek]

bump on this one...this is similar to this one too...https://github.com/GoogleCloudPlatform/k8s-config-connector/issues/166

[kibbles-n-bytes]

Hey @thecloudgeek ; unfortunately we don't yet have any updates on this front, but we'll keep you posted.

[AlexBulankou]

FYI @mountainsaxena

[skeenan947]

Is anything going to be done about this? It's a pretty big bit to be missing.

[toumorokoshi]

Hi! It's been a while on this issue, thanks for pinging to show you need it.

I'll talk to the team a bit and come back. Agreed this is a use case that should be supported.

[toumorokoshi]

Hello,

Just a quick update: we've taken a look at right approach, and we believe that it's appropriate to change the schema of the rrdatas list to support an object. Since that would be a backwards-incompatible change, we'd like to pair that with some work to support multiple versions for the same CRD.

We've tentatively set the timeline for sometime near the end of Q1. I'll update this ticket as the timeline becomes more clear.

[skeenan947]

Thank you! Great to hear.

[skeenan947]

Any update on the timeline for this? We've got a hacky workaround to this but really need this across a ton of our applications. Thanks!

[jcanseco]

Hi @skeenan947, I apologize that we missed your question. Unfortunately, we don't have a real ETA on a solution yet. We have been keeping the issue in mind, and we have been discussing possible solutions. Our capacity's just been quite tight recently, so we haven't been able to invest the time needed to develop the infrastructure needed to resolve issues like this. Once we make more headway, we'll make sure to let you know. Unfortunately, you'll have to rely on the hacky workaround for the moment.