Test if experimentalRetryJoin still needed for K8s 1.19+

[randomvariable]

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Run some e2e tests and see if experimentalRetryJoin is still needed as per https://kubernetes.slack.com/archives/C8TSNPY4T/p1601486982126900

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):

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[randomvariable]

Somebody already removed this. Who knows.

/close

[k8s-ci-robot]

@randomvariable: Closing this issue.

In response to this:

Somebody already removed this. Who knows.

/close

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.