You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating the zone works, but it's requesting nameservers update in Cloudflare UI.
When trying to delete that zone it triggers reconciling event but the resource could not be found in cloudflare and therefore is not deleted.
In general I think we should find a way to send meta data along with the API requests so we can tell which resources are managed by the automated operator and which ones are not, and consider only those which are managed by the k8s operator.
This will allow flexibility for people who already have some resources manually created on cloudflare, and they want to start using the gitops approach (mix of both worlds).
This is how external-dns is handling this kind of scenarios. If the resource was not initially created by their operator, they do not consider it as a managed resource.
The text was updated successfully, but these errors were encountered:
Followup to #6
Creating the zone works, but it's requesting nameservers update in Cloudflare UI.
When trying to delete that zone it triggers reconciling event but the resource could not be found in cloudflare and therefore is not deleted.
In general I think we should find a way to send meta data along with the API requests so we can tell which resources are managed by the automated operator and which ones are not, and consider only those which are managed by the k8s operator.
This will allow flexibility for people who already have some resources manually created on cloudflare, and they want to start using the gitops approach (mix of both worlds).
This is how external-dns is handling this kind of scenarios. If the resource was not initially created by their operator, they do not consider it as a managed resource.
The text was updated successfully, but these errors were encountered: