Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌱 chore: configure janitor to cleanup aws resources #413

Merged
merged 1 commit into from
Mar 5, 2024

Conversation

salasberryfin
Copy link
Contributor

What this PR does / why we need it:

Enable aws-janitor to clean resources using a mark and delete approach (first execution mark/next delete), including:

  • EKS clusters.
  • Auto Scaling Groups.
  • Load Balancers.
  • Security Groups.
  • CloudFormation stacks.

Resources that include the tag janitor-ignore will be skipped.

Which issue(s) this PR fixes:
Fixes #368

Special notes for your reviewer:

This PR is waiting on an initial release of https://github.com/rancher-sandbox/aws-janitor, which will be created after rancher/aws-janitor#4.

aws-janitor runs after azure-janitor. It will run even if the previous job fails and it'll be skipped only if the action is cancelled.

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@salasberryfin salasberryfin requested a review from a team as a code owner March 4, 2024 19:47
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
@richardcase richardcase merged commit 94e45a0 into rancher:main Mar 5, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setting up AWS janitor
3 participants