Allow creating Route53 RecordSet from ConfigMap data

[philchristensen]

Is your feature request related to a problem?

In my GitOps pipeline, I use ACK to deploy an RDS instance. I'd like to also deploy a Route53 RecordSet with a CNAME for this, but since the native DB hostname isn't known until it's created, I need to use the data that is saved in a ConfigMap using the FieldExport objects.

Describe the solution you'd like

The RecordSet CRD should support pulling values from ConfgMaps (maybe also from Secrets), e.g.:

  resourceRecords:
  # currently supported
  - value: string
  # (required) support pulling from ConfigMaps   
  - valueFrom:
      configMapKeyRef:
        name: myconfigmap
        key: myvalue
  # (optional) also support pulling from Secrets?
  - valueFrom:
      secretKeyRef:
        name: mysecret
        key: myvalue

Describe alternatives you've considered

I really can't think of how to get a ConfigMap value to be used in any other way, but I'm open to suggestions if I'm missing something.

[github-actions]

Hello @philchristensen 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[rushmash91]

Thanks for raising this feature request! Currently, ACK doesn't support direct ConfigMap references in Route53 RecordSets.

For your use case, I'd recommend checking out KRO. It's specifically designed to handle workflows like yours. KRO might be a better immediate solution for your GitOps pipeline.

The examples here might help: https://github.com/kro-run/kro/tree/main/examples/aws. Let me know if you run into any issues 🙂.

[philchristensen]

Just a heads up that while I did find a workaround via KRO, because of existing issues like kubernetes-sigs/kro#535 it is extremely verbose and kind of hard to understand for new users.

In my case (this is a Helm chart) I think for now I'm just going to require my users pass in the "hex-string" that RDS uses so I can calculate what the DNS name will be.

I'd still be eager to help test if anyone had a chance to try to implement this feature natively!

[arichtman-srt]

+1 - we would like to use this to generate domain verification records for an ACM certificate

[Ashish7812]

@philchristensen What workaround did you find using KRO (Kube resource orchestrator)? I'm trying to reference data from a ConfigMap, but I haven't been able to get it working.

[philchristensen]

@philchristensen What workaround did you find using KRO (Kube resource orchestrator)? I'm trying to reference data from a ConfigMap, but I haven't been able to get it working.

In most cases when you use KRO you don’t really need to create or read from a ConfigMap. Instead you’d include the resource you’re creating and the resource you want to use its value in within the same resource group. This didn’t work for me because I was trying to use it inside a Helm chart, and I would have had to create the RGD in ways that I didn’t like.

Recently I’ve found KRO useful for other things, but it was too verbose for me to use with DBInstance.

[arichtman-srt]

I've approached this with a general purpose operator that creates and manages any resource based on ConfigMap inputs.

My issue now is that the Certificate resource's .status.domainValidations[0].resourceRecord.name path contains the entire domain with the root ., which I can't feed into the RecordSet's .spec.name without manipulation.

E.g.

domainValidations:
  - domainName: mydomain.example
    resourceRecord:
      name: _1440c922da6e9db179793a4daf47dc78.mydomain.example.
      type_: CNAME
      value: _778cd800d331e33154603e2e0e41c857.xlfgrmvvlj.acm-validations.aws.

I can FieldExport the name _1440c922da6e9db179793a4daf47dc78.mydomain.example. just fine, but when making a RecordSet using that name it bombs, trying to create an entry like _1440c922da6e9db179793a4daf47dc78.mydomain.example..mydomain.example.

InvalidInput: FATAL problem: DomainLabelEmpty (Domain label is empty)

It'd be nice if an additional status field contained precisely the RecordSet name required, but I suspect it's out of scope of ACK.