Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Route53] Support multiple Zone IDs in spec #1853

Closed
Ethan-99 opened this issue Aug 30, 2023 · 2 comments
Closed

[Route53] Support multiple Zone IDs in spec #1853

Ethan-99 opened this issue Aug 30, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@Ethan-99
Copy link

What problem are you facing?

In the ResourceRecordSet resource, the name of the resource is the name of the record. This is all well and good, unless you want to be able to create more than one record of the same name in different zones. Say I have an ArgoCD app and a r53 record controlled by that app. I want to put this record in both Zone A and Zone B. I am unable to create two instances of ResourceRecordSet because the names of the resources are the same, and you can only provide one Zone ID to place the record in the resource object.

How could Crossplane help solve your problem?

It would be great if this can be supported by implementing the following to the resource manifest:

Add a new optional parameter to the ResourceRecordSet resource called zoneIds or something similar that accepts a list of zone IDs to create the record. Add constraints such that only one of zoneId, zoneIds, zoneIdRef, or zoneIdSelector may be defined.

@Ethan-99 Ethan-99 added the enhancement New feature or request label Aug 30, 2023
@haarchri
Copy link
Member

you can use crossplane.io/external-name annotation then you can set metadaten.name to random string

@Ethan-99
Copy link
Author

Ethan-99 commented Sep 1, 2023

@haarchri Thank you, exactly what I needed. Did not realize this functionality was available.

@Ethan-99 Ethan-99 closed this as completed Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants