NOJIRA: Create token Secret for dev cluster explicitly

[mgencur]

Needs to be created manually because:
Prior to OpenShift Container Platform 4.16, a long-lived service account API token secret was also generated for each service account that was created. Starting with OpenShift Container Platform 4.16, this service account API token secret is no longer created.

Related Slack discussion

What this PR does / why we need it:
With the new version of OpenShift, the Secret/Token is not created automatically.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[csrwng]

/area ci

[openshift-ci]

@csrwng: The label(s) area/ci cannot be applied, because the repository doesn't have them.

In response to this:

/area ci

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.

[csrwng]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, mgencur

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [csrwng]

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

[devguyio]

/area ci-tooling

[devguyio]

/retitle "NOJIRA: Create token Secret for dev cluster explicitly"

[devguyio]

/retitle NOJIRA: Create token Secret for dev cluster explicitly

[mgencur]

/test okd-scos-e2e-aws-ovn

The error error doesn't seem to be related to my changes.

[openshift-ci]

@mgencur: all tests passed!

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