Michael Tewoldemedhin

@mqhenning The docs are outdated, there's a PR that will update it soon! The feature is supported across all controllers

It looks correct, except you'd need the recordSet ID instead of name. ```yaml apiVersion: route53.services.k8s.aws/v1alpha1 kind: RecordSet metadata: name: my-recordset annotations: services.k8s.aws/adoption-policy: "adopt" services.k8s.aws/adoption-fields: | { "id": "foo", "recordType": "CNAME",...

The issue might be the feature flags not being enabled? Here's an updated doc: https://aws-controllers-k8s.github.io/community/docs/user-docs/features/ Can you share the manifest you used? Edit: From the error message, it seems like...

The syntax seems correct to me..also it seems like you're using an older controller..can you update to [v0.0.26](https://gallery.ecr.aws/aws-controllers-k8s/route53-chart) and share the output of the kubectl get {resource} -oyaml?

Is the featureGate enabled? https://github.com/aws-controllers-k8s/route53-controller/blob/2a0ffc1cd663367dccd7287a4d6669a45a7355e6/helm/values.yaml#L172 That could be the only other issue i can think of..

That's weird. I just attempted to replicate it and I was able to adopt a recordSet with NS type, but not CNAME. I'll look further into this..

Fix incoming! you would just need to add one more field :) (recordSetName)!

No, I've mostly use a placeholder for ID, since i couldn't retrieve it from the console. The controller deems it required during adoption but it does not really use it...

Closing as resolved /close

Hello @Chalapathidevops, The MSK cluster references SecretsManager Secrets, not Kubernetes Secrets. Here's a use case example: MSK Cluster: ```yaml apiVersion: kafka.services.k8s.aws/v1alpha1 kind: Cluster metadata: name: my-kafka-cluster spec: name: my-kafka-cluster ......