allow ack route53 to access fields from ack acm for domain validation

[FernandoMiguel]

Is your feature request related to a problem?
ACK controllers require inputs. those are only from values.yaml. Sometimes that data is in configmaps.

Describe the solution you'd like
All ACKs have FieldExport that stores Status values in ConfigMaps and Secrets.
But this is of no use for other ACKs as input.
For example, when using ACK ACM and storing the validation DNS records into a ConfigMap, you can't use that in ACK Route53, or the Certificate ARN in the ACK LBC.
Ideally, all ACK CRDs should be able to take inputs from either values.yaml or ConfigMap.

Describe alternatives you've considered
Using Terraform or having to support quirky Watcher controllers to copy this data around

[github-actions]

Hello @FernandoMiguel 👋 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.

[michaelhtm]

Hi @FernandoMiguel, kro can be used to allow users to pass fields from one resource to another.
There are some ACK examples in it as well here.
Would that assist you in your use case?

[FernandoMiguel]

hi @michaelhtm
my understanding is that kro is still very new and evolving very quickly, maybe not something appropriated for a production env.
If ACK CRDs were to be modified to accept input from multiple sources, this would be native to the ACK implementation without the need for an extra controller

[michaelhtm]

I understand..currently there is a way for some ACK resources to reference another ACK resource's fields (Eg. EKS Cluster can reference Subnet shown here)

We can still add references support for fields as long as it makes sense, it just won't be dynamic.

The issue for making references dynamic was tracked here: #1576

[FernandoMiguel]

I understand..currently there is a way for some ACK resources to reference another ACK resource's fields (Eg. EKS Cluster can reference Subnet shown here)

@michaelhtm I was not aware of this ability.
Can we add ack route53 reference to ACK ACM validation records?
that would solve my immediate issue (and one that affects everyone who wants to issue certificates)!!

should I open a new card for that, or rewrite this?

[FernandoMiguel]

for future reference for anyone coming across this, there is a dedicated kro example for my request
https://github.com/kro-run/kro/blob/main/examples/aws/ingress-triangle/README.md

[michaelhtm]

should I open a new card for that, or rewrite this?

This one should be okay..maybe just a title change :)

We can attempt to solve this..

[michaelhtm]

Hi @FernandoMiguel
After looking at your kro example, i noticed you're trying to reference multiple fields inside list. List value references are not supported in ACK.
https://github.com/kro-run/kro/blob/1a138cfe789964d17ae274022e6b3c298c6f60b8/examples/aws/ingress-triangle/ingress-triangle.yaml#L42-L44
cc: @a-hilaly @rushmash91

[FernandoMiguel]

Hi @FernandoMiguel
After looking at your kro example, i noticed you're trying to reference multiple fields inside list. List value references are not supported in ACK.
cc: @a-hilaly @rushmash91

@michaelhtm wrong thread maybe?

[michaelhtm]

not really..
I looked at the kro example and noticed your are trying to reference ACM Certificate.Status.DomainValidations[$index].resourceRecord.*
In ACK when we do references we don't support fields inside a list AFIK..
This is the struct that we use to reference a resource, which currently is not index specific..https://github.com/aws-controllers-k8s/runtime/blob/07dcd404a9a7bc3efe890791b910f9ec41712926/apis/core/v1alpha1/identifiers.go#L74-L77

To support your use case, we would need to add index here..

[ack-bot]

Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale