WIP: Experiment, switch use-service-account-credentials flag

[lobziik]

see: https://github.com/kubernetes/cloud-provider/blob/0ceab8edbfaff060e897f17ed0d25308d07eb678/options/options.go#L183-L190

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from lobziik after the PR has been reviewed.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[lobziik]

/retest

[lobziik]

/test unit

[lobziik]

/retest

[lobziik]

/retest

[openshift-ci]

@lobziik: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ccm	6fc4527	link	false	/test e2e-vsphere-ccm
ci/prow/e2e-gcp-ccm-install	6fc4527	link	false	/test e2e-gcp-ccm-install
ci/prow/e2e-azure-ccm-install	6fc4527	link	false	/test e2e-azure-ccm-install
ci/prow/e2e-aws-ccm-install	6fc4527	link	false	/test e2e-aws-ccm-install
ci/prow/e2e-vsphere-ccm-install	6fc4527	link	false	/test e2e-vsphere-ccm-install
ci/prow/e2e-azure-ccm	6fc4527	link	false	/test e2e-azure-ccm
ci/prow/e2e-aws-ccm	6fc4527	link	true	/test e2e-aws-ccm
ci/prow/e2e-gcp-ccm	6fc4527	link	false	/test e2e-gcp-ccm

Full PR test history. Your PR dashboard.

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

[JoelSpeed]

@lobziik What was the conclusion of this test? Do we still need this PR?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.