When PriorityClass (or any other yaml) fails to be deployed on the cluster the rest of driver set-up continues

[davidz627]

we see this a lot in clusters with version too low for priorityClass. The priorityClass fails to deploy but the error is not caught until we complete deployment of the driver and it fails to come up because it can't find the referenced priorityClass. We should make this experience better

/cc @yuga711

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[msau42]

/lifecycle frozen
/kind cleanup