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

aws-samples / nexus-oss-on-aws

Deploy Sonatype Nexus Repository OSS on AWS with well architecture.

https://www.amazonaws.cn/en/solutions/nexusoss-on-aws/

MIT No Attribution

57 stars 20 forks source link

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

Open DmitriyStoyanov opened 3 years ago

DmitriyStoyanov commented 3 years ago

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

[ ] :wave: I may be able to implement this feature request

This is a :rocket: Feature Request

github-actions[bot] commented 3 years ago

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[bot] commented 2 years ago

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[bot] commented 2 years ago

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[bot] commented 2 years ago

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 commented 2 years ago

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