Correct Failing E2E Tests

[rlymbur]

What type of PR is this?
Bug

Which issue does this PR fix:
#673

What does this PR do / Why do we need it:
Increases timeout on E2E tests and adds a custom retryer to address these failures.

Testing done on this change:

make e2e-test ... Ran 69 of 69 Specs in 3036.131 seconds SUCCESS! -- 69 Passed | 0 Failed | 0 Pending | 0 Skipped --- PASS: TestIntegration (3036.14s) PASS ok github.com/aws/aws-application-networking-k8s/test/suites/integration 3036.770s 

Automation added to e2e:

N/A

Will this PR introduce any new dependencies?:

No.

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No.

Does this PR introduce any user-facing change?:

No.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[erikfuller]

Thanks for digging into this. Really just my one question around the retryer code to address before moving ahead.

[iph]

LGTM, had a clarifying question around amount of retries but that's about it.

[iph]

What's the default retries we are overriding?

I get that these are integration tests -- but 3 is "quite a bit".

[rlymbur]

The default retries is actually already three, probably best I remove it here to avoid any confusion. For some more context:

const (	// DefaultRetryerMaxNumRetries sets maximum number of retries	DefaultRetryerMaxNumRetries = 3	// DefaultRetryerMinRetryDelay sets minimum retry delay	DefaultRetryerMinRetryDelay = 30 * time.Millisecond	// DefaultRetryerMinThrottleDelay sets minimum delay when throttled	DefaultRetryerMinThrottleDelay = 500 * time.Millisecond	// DefaultRetryerMaxRetryDelay sets maximum retry delay	DefaultRetryerMaxRetryDelay = 300 * time.Second	// DefaultRetryerMaxThrottleDelay sets maximum delay when throttled	DefaultRetryerMaxThrottleDelay = 300 * time.Second ) 

[mikestvz]

LGTM 🚀

Issue addressed