aws-controllers-k8s
What to do with the data plane?
Is your feature request related to a problem? ACK provides support for provisioning of the resources. While connecting to some of these resources we may see issues related to source ip not whitelisted and related issues with dynamically-changing client instances/Pods.
Describe the solution you'd like There may be multiple options
- Do nothing, rely on customer to handle connectivity.
- Use an open source proxy
- Build something as a subproject of sorts within ACK
- Build something entirely separate and link to it from ACK docs
A description of what you want to happen. Connect from client instances/Pods to provisioned resources.
Worth investigating: https://github.com/redhat-developer/service-binding-operator
We may not need/want to do anything with the data plane at all if the above can handle data plane operations.
FieldExport was designed to fix this problem. Check out the pull request for it here:
https://github.com/aws-controllers-k8s/runtime/pull/75
And the documentation for it here: https://aws-controllers-k8s.github.io/community/reference/common/v1alpha1/fieldexport/
@RedbackThomson @a-hilaly Hi! Noticed this ticket. It looks like that FieldExport documentation is not enough and the resource does not give option to combine two arbitrary resources. Like to put vpcID not to Secret/ConfigMap, but to something more interesting like resourcesVPCConfig field of Cluster
We are looking upstream at our work on KRO (github.com/kro-run/kro) to solve for these sorts of issues. Will close this tracking issue for now.
