Define the prow testing infrascture using ACK controllers/resources.

a-hilaly commented 9 months ago

The current ACK test setup relies on CDK for creating resources from various services like EKS, IAM, S3, VPC, EC2, etc. Now that ACK controllers are maturing and seeing more and more adoption in the kubernetes world, we should start using our own controllers to deploy the testing infrastructure. This serves three main purposes:

1) Help identifies controller bugs and issues to help improve the controllers overall
2) Showcase real-world production examples to ACK users.
3) Leverage ACK powerful create/update paths and drift remediation loops.

We can achieve the above by breaking into the following sub tasks:

Investigate the creation of a management cluster using ACK, possibly starting with a kind cluster and adopting it later in EKS.
Utilize Helm for the straightforward deployment of necessary ACK controllers.
Explore defining IAM Roles and Service Accounts using ACK.
Implement a GitOps approach using FluxCD for updating ACK testing infrastructure.

ack-bot commented 3 months ago

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

ack-bot commented 1 month ago

Stale issues rot after 60d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 60d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

aws-controllers-k8s / community

Define the prow testing infrascture using ACK controllers/resources. #1979