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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Route53 Zone external name not being set after creation #1567

Open

1 task done

awprice opened this issue Nov 17, 2024 · 0 comments

Open

1 task done

[Bug]: Route53 Zone external name not being set after creation #1567

awprice opened this issue Nov 17, 2024 · 0 comments

Labels

bug needs:triage

awprice commented Nov 17, 2024 •

edited

Loading

Is there an existing issue for this?

I have searched the existing issues

Affected Resource(s)

route53.aws.upbound.io/v1beta1 - Zone

Resource MRs required to reproduce the bug

apiVersion: route53.aws.upbound.io/v1beta1
kind: Zone
metadata:
  name: example
spec:
  forProvider:
    name: mycompany.test
    region: us-west-1

Steps to Reproduce

Apply MR (Zone) to cluster
Hosted Zone is created in AWS Route53 by provider
MR becomes synced: true and ready: true

What happened?

External name annotation is never added to MR
Crossplane will eventually create duplicate hosted zones if the provider is restarted

Relevant Error Output Snippet

No response

Crossplane Version

v1.16.1

Provider Version

v1.17.0

Kubernetes Version

v1.29.8

Kubernetes Distribution

EKS

Additional Info

This issue is similar to #1482

The text was updated successfully, but these errors were encountered:

awprice added bug needs:triage labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment