-
Notifications
You must be signed in to change notification settings - Fork 263
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 controller can't import readonly HostedZone resource #2301
Comments
Hello @mano1233, the way ReadOnlyResources works is by annotating an already existing resource with read-only. So you would need to create the resource first, and once it's synced, annotate it as readOnly. |
Hi @mano1233, You would have to enable the following values when you install the helm chart:
Then to import the resource, you need to create the following yaml with empty spec:
That will import the hosted zone, and you should see the name of the hosted zone under spec. |
Hey, Good to know, Is this the same for all controllers? |
This is a feature flag that needs to be enabled for each controller. At the moment import only supports by id, tag is not supported. Working with the team to review #2297 |
Hey @mano1233, i don't think all services support adoption/import by tags, the only one i know of is ec2.. |
Hey @mano1233, i'm marking this issue as stale, please feel free to remove it if the issue is not resolved for you and reply on this thread for any more questions. Thanks! |
Describe the bug
When Using the ReadOnlyResources Feature flag, When trying to create a hosted zone with read-only annotation. The controller sends an error that the hosted zone is not found.
Steps to reproduce
ReadOnlyResources
feature flag enabled.services.k8s.aws/read-only: "true"
Expected outcome
Manage to find the resource and update the status field with the relevant hosted zone id.
HostedZone CR
Error logs
Environment
The text was updated successfully, but these errors were encountered: