Parallelizing resource creation

[sedefsavas]

/kind feature

There is room for improvement for AWSCluster/AWSMachine creation time by parallelizing resource creation furter.

Similar to NAT gateway creation parallelization, we can evaluate which resource can be created without waiting which others with a dependency graph.

Some examples on what we can do further:

1. SecurityGroups creation can start right after VPC creation is complete.
2. createSubnets() can be parallelized.
3. ELB creation can be started right after subnets are created.
4. Internet gateway and NAT gateway creation can be parallelized as well.

[k8s-ci-robot]

@sedefsavas: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sedefsavas]

/remove-lifecycle stale