Ansible-playbook fails to make Trident run.

[Mauricio Biasi do Monte Carmelo]

Brief Description
-----------------
After running the command,

$ansible-playbook /usr/share/ansible/stx-ansible/playbooks/install_netapp_backend.yml

the Trident's pods are not created.

Ansible logs:

unable to recognize "/tmp/snapshot-controller/crd/snapshot.storage.k8s.io_volumesnapshotclasses.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1

 unable to recognize "/tmp/snapshot-controller/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1

unable to recognize "/tmp/snapshot-controller/crd/snapshot.storage.k8s.io_volumesnapshots.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1

Severity
--------
major

Steps to Reproduce
------------------
n/a

Expected Behavior
------------------

Trident pods created successfully:

kubectl get pod -n=trident -o=wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
trident-csi-5llnq 2/2 Running 0 111m 192.168.204.93 compute-0 <none> <none>
trident-csi-68f68c94f9-l5jmk 5/5 Running 0 111m 172.16.166.191 controller-1 <none> <none>
trident-csi-7hm6v 2/2 Running 0 111m 192.168.204.4 controller-1 <none> <none>
trident-csi-8nsls 2/2 Running 0 111m 192.168.204.59 compute-3 <none> <none>
trident-csi-fmslx 2/2 Running 2 111m 192.168.204.3 controller-0 <none> <none>
trident-csi-v4625 2/2 Running 0 111m 192.168.204.73 compute-1 <none> <none>
trident-csi-ww2tq 2/2 Running 4 111m 192.168.204.57 compute-2 <none> <none>

Actual Behavior
----------------
kubectl get pod -n=trident -o=wide'
No resources found in trident namespace.

Reproducibility
---------------
100%

System Configuration
--------------------
n/a

Branch/Pull Time/Commit
-----------------------
n/a

Last Pass
---------
n/a

Timestamp/Logs
--------------
n/a

Test Activity
-------------
n/a

Workaround
----------
Downgrade Kubernetes to a version lower than v1.22.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/855979
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/2e2f4f9367bce9eb9d7d5c16aaba4c084441f0c2
Submitter: "Zuul (22348)"
Branch: master

commit 2e2f4f9367bce9eb9d7d5c16aaba4c084441f0c2
Author: mbiasido <email address hidden>
Date: Mon Sep 5 15:46:57 2022 -0400

    Migrate CRDs to use API version apiextensions.k8s.io/v1

    K8s stopped serving API apiextensions.k8s.io/v1beta1 since version v1.22.
    Use apiextensions.k8s.io/v1 instead of apiextensions.k8s.io/v1beta1.

    Migrated the following files to use apiextensions.k8s.io/v1:

    snapshot.storage.k8s.io_volumesnapshotclasses.yaml
    snapshot.storage.k8s.io_volumesnapshotcontents.yaml
    snapshot.storage.k8s.io_volumesnapshots.yaml
    configure-snapshot-storage-classes.yml

    The new CRDs files were collected from
    kubernetes-csi/external-snapshotter version v6.0.1:
    https://github.com/kubernetes-csi/external-snapshotter/releases/tag/v6.0.1

    Closes-Bug: #1988875

    Test Plan:
    PASS: Installed Trident 22.01.0 with Kubernetes v1.23.1 running.
    PASS: Connected to Netapp, creating a PVC instance.
    PASS: Wrote information into the database.
    PASS: Removed the PVC instance and uninstalled Trident.
    PASS: Tested Trident 22.01.0 with Kubernetes v1.21.8.
    PASS: Tested Trident 22.01.0 with Kubernetes v1.22.5.
    PASS: Tested on Debian WRCP 21.12.

    Signed-off-by: Mauricio Carmelo <email address hidden>
    Change-Id: I6c1ae3bdd8bf38a235a0ec65ea1a9487b6ce773e