Extend CABPK timeout to 30m to account for etcd cluster settling in vSphere environments.

[randomvariable]

Signed-off-by: Naadir Jeewa [email protected]

What this PR does / why we need it

Which issue(s) this PR fixes

Fixes #954

Describe testing done for PR

Release note

PR Checklist

• Squash the commits into one or a small number of logical commits
  
• Use good commit messages
• Ensure PR contains terms all contributors can understand and links all contributors can access

Additional information

Special notes for your reviewer

[github-actions]

Cluster Generation A/B Results:
https://storage.googleapis.com/tkg-clustergen/955/20211022143020/clustergen.diff.txt
Author/reviewers:
Please review to verify that the effects on the generated cluster configurations are exactly what the PR intended, and give a thumbs-up if so.

[vuil]

Thanks for the changes, and the explanations in #954

[pydctw]

/test

[pydctw]

Changes looks good to me.

@vuil

1. Is there a command to re-trigger failing tests?
2. Looks like I don't have an access to view this file - https://storage.googleapis.com/tkg-clustergen/955/20211022143020/clustergen.diff.txt

[alfredthenarwhal]

@pydctw: /test
Commit: 9d08a6e

Tests failed! Build no: 955

[vuil]

Changes looks good to me.

@vuil

1. Is there a command to re-trigger failing tests?

You can click the failed check(s), and click "rerun all jobs" on the top right. Are you seeing the option? I just reran the failed checks, and it does look like this change may be responsible for some integration/e2e tests failing

2. Looks like I don't have an access to view this file - https://storage.googleapis.com/tkg-clustergen/955/20211022143020/clustergen.diff.txt

It's not that. The UX of the link can possibly but improved, but if the PR does not result in any differences in any cluster configuration generation, the file will show blank today.
As for why it is blank for this change, this is because clustergen only captures the dry-run output of "cluster create", iow that which is produced via yttprocessor processing the infra-specific cluster template along with the associated overlays.
So changes in yaml deploying actual CAPI components such as this PR are not captured, unfortunately.

[pydctw]

You can click the failed check(s), and click "rerun all jobs" on the top right. Are you seeing the option? I just reran the failed checks, and it does look like this change may be responsible for some integration/e2e tests failing

I don't see "rerun all jobs" option. This is the first time I am reviewing PRs in tanzu-framework so trying to get familiarized with different label/commands.

Thanks for the explanation on the clustergen.diff file. Makes sense.