Support of usage existing external-dns, efs-csi-driver and aws-load-balancer-controller in existing EKS cluster

[DmitriyStoyanov]

Use Case

For the moment we already have existing EKS cluster with alb-ingress-controller and external-dns controller with custom configuration managed by separate IaC solution.
To add this nexus solution in our cluster, we need to have ability to use existing controllers instead of deployment from nexus-oss-on-aws repo.

Proposed Solution

Other

• 👋 I may be able to implement this feature request

---

This is a 🚀 Feature Request

[github-actions]

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.

[github-actions]

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.

[github-actions]

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.

[github-actions]

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

[zxkane]

in roadmap #142 the nexus oss will be packaged as construct to address this request