Graduate the garbage Collection feature

[richardcase]

/kind feature

Describe the solution you'd like We introduced GC in v1.5.0 in Aug 2022. I propose that we graduate this feature and enable it by default.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[richardcase]

/assign

[richardcase]

/milestone v2.3.0

[richardcase]

/triage accepted

[richardcase]

/priority important-soon

[Ankitasw]

@richardcase do we have a task list to track what all fixes should go as part of this?

[Fedosin]

@Ankitasw I think the remaining tasks are:

1. Add validation for GC config (https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4485)
2. Add awscli support for GC configuration.
3. Update the docs.

Tell me if I missed something.

[richardcase]

/milestone v2.4.0

[Ankitasw]

@Ankitasw I think the remaining tasks are:

Add validation for GC config (https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4485) Add awscli support for GC configuration. Update the docs. Tell me if I missed something.

@Fedosin would you be able to proceed with these tasks?

[richardcase]

/unassign

[richardcase]

/help

[k8s-ci-robot]

@richardcase: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/4397): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[richardcase]

/triage accepted /priority important-soon

[richardcase]

/milestone v2.5.0

[richardcase]

/assign /lifecycle active

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[richardcase]

/triage accepted