Meeting Notes === ###### tags: `Resource Reference` `Brainstorming` `K8s Native` ## Reference ACK Resource(s) In K8s Native Resource(s) * Possibility of supporting cross namespace, infra in one namespace and application in another namespace * Explore idea of annotations that export spec/status fields to configMap/Secret * Explore idea of creating another CRD that creates a binding between ACK resource and K8s native resources * Should existing service binding work be used or create our own CRD * Should current resource reference UX be ungraded to line with generic resource reference? IOW, should referencing cross controller resources be done with service binding? * Nick volunteered to do more research on the above ideas ### Important Links * [ACK Issue #740](https://github.com/aws-controllers-k8s/community/issues/740) * https://github.com/servicebinding/spec * https://redhat-developer.github.io/service-binding-operator/userguide/intro.html * https://servicebinding.io