Ability to specify name and namespace of output secret

[ryanfaircloth]

Just as the title asks can we allow the name and namespace of the secret to be specified

[scholzj]

I do not think this would work really well with the operator pattern where things need to be deterministic. If you want the secret in another namespace, create the custom resource there.

[katheris]

Triaged on 20.2.2025: We wouldn't add a namespace option for the reasons Jakub described. For the name @ryanfaircloth what was the usecase for wanting a different name than the one you use for the KafkaAccess CR?

[ryanfaircloth]

The use case is flexibility to work with existing deployments that expect specific names. So a migration use case

[im-konge]

Triaged on 6.3.2025: The name of the secret matches the name of the KafkaAccess CR, however it makes sense to have an option for specifying the name. For the Namespace part, we don't think that would make sense to have it in the API. Keeping it open for adding the possibility to specify the Name in the KafkaAccess CR.