ACK importing resources per tag feature

[alicvsroxas]

Problem description
During our development and testing with ACK, we ran into a particular use case.
Originally, when running our infrastructure using Terraform, we relied on a small amount of data sources that retrieves information from AWS.
For example, getting VPC ID, subnets IDs, roles ARNs and so forth.
We are trying to find an alternative for this use case when it comes running our systems using ACK.

We would like to hear your thoughts on an ACK feature that gets information from AWS objects that were created previously,
and store them in either Kubernetes Configmaps, or Kubernetes Secrets, to be later used by other deployments that require that information.

Solutions
A new Custom Resource Definition that receives a certain "Selector Terms".
For example, get me all subnet IDs that have a tag that I specify in the Custom Resource,
and place them in a Kubernetes Configmap which I can later mount or make use of using, for example, Kro,
for any deployment that needs that information in order to function.

We believe it can remove the overhead of managing a hardcoded Configmap which we will need to update each time,
and instead rely on an automatic solution, with AWS cloud access, to fetch that information reliably.

[rushmash91]

Hi @alicvsroxas,
Thank you for bringing this up!

I understand the use case and see how this could streamline managing AWS resource information dynamically. I'll raise this with the ACK and Kro teams to explore potential solutions and get back to you. In the meantime, feel free to create an issue on the Kro GitHub repository to track this idea and gather feedback from the community.

[michaelhtm]

Hi @alicvsroxas, closing this issue for now. Feel free to reopen it if not yet resolved. Thanks!
/close

[ack-prow]

@michaelhtm: Closing this issue.

In response to this:

Hi @alicvsroxas, closing this issue for now. Feel free to reopen it if not yet resolved. Thanks!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[michaelhtm]

/reopen

[ack-prow]

@michaelhtm: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alicvsroxas]

Hello, thank you for reopening the case.
I now see in ACK there is a read-only feature for resources, and wondered if it would be possible to add this feature request to that future mechanism.
As well as having that mechanism of getting/reading the resource by name, add the option to find resources by tags.
As many resources in AWS can have tags configured, if it's EKS, Subnets, EC2, VPC, Security Groups, Load Balancers, and so forth.

[alicvsroxas]

/reopen

[ack-prow]

@alicvsroxas: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.