[HIVE-2944] Make the cluster in e2e-pool use legacy deprovision

[suhanime]

As a part of AWS SDK v2 migration, installer changed some of the fields populated by the destroyer builder that diverges from our existing destroy flow. Add an annotation for legacy deprovision on a cd created by e2e pool, to ensure both deprovision paths work as expected.

Also capture deprovision pod yaml

[suhanime]

/test e2e-pool

[2uasimojo]

See HIVE-3069 for the security fail.

The e2e-pool fail looks like we're timing out deprovisioning... which is exactly what we would expect if legacy deprovision isn't working. But we don't have good FFDC for that yet. Suggest adding collection of

• ClusterDeprovisionz here
• deprov pod logs here.

[2uasimojo]

/lgtm
/override ci/prow/security
/test hive-mce-27-on-pull-request
/test hive-mce-28-on-pull-request

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo, suhanime

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [2uasimojo,suhanime]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@2uasimojo: Overrode contexts on behalf of 2uasimojo: ci/prow/security

Details

In response to this:

/lgtm
/override ci/prow/security
/test hive-mce-27-on-pull-request
/test hive-mce-28-on-pull-request

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-sigs/prow repository.

[2uasimojo]

/test hive-mce-27-on-pull-request

/test hive-mce-28-on-pull-request

[2uasimojo]

/test hive-mce-28-on-pull-request

[suhanime]

/test hive-mce-27-on-pull-request

[openshift-ci]

@suhanime: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.