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 resource does not work well with wildcard '*' #1115

Closed
mario-bris opened this issue Feb 2, 2022 · 1 comment · Fixed by #1370
Closed

route53 resource does not work well with wildcard '*' #1115

mario-bris opened this issue Feb 2, 2022 · 1 comment · Fixed by #1370
Labels
bug Something isn't working

Comments

@mario-bris
Copy link

What happened?

I am trying to create CNAME with wildcard so I do not have to explicitly create each route53 entry. E.g. I have DNS entry myproject.mycompany.com which is A type of record. I'd like to have wildcard DNS records (type of CNAME ) for apps (app1, app2, ...), e.g. *.myproject.mycompany.com however when I create such record via route53.aws.crossplane.io/v1alpha1 and kind ResourceRecordSet its state is READY: False. The same behaviour is for CNAME and A record.

test-dns                                 False   True     *.myproject.mycompany.com   CNAME      11m

However DNS entry is create in AWS but It's not deleted when I delete ResourceRecordSet resource.

How can we reproduce it?

You can use following manifest

apiVersion: route53.aws.crossplane.io/v1alpha1
kind: ResourceRecordSet
metadata:
  name: 'test-dns'
  annotations:
    crossplane.io/external-name: "*.myproject.mycompany.com"
spec:
  forProvider:
    type: A
    ttl: 300
    zoneId: <zoneId>
    resourceRecords:
    - value: 1.2.3.4
  providerConfigRef:
    name: default

What environment did it happen in?

Crossplane version: crossplane/provider-aws-controller:v0.22.0
Aws provider version: crossplane/crossplane:v1.5.1

@mario-bris mario-bris added the bug Something isn't working label Feb 2, 2022
@mithie
Copy link

mithie commented Jun 23, 2022

I am facing the exact same problem. A CNAME wildcard recordset is going to be created, but will never be in READY: true state. Deletion of the crossplane resource won't delete the AWS resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants