Updating csi-provisioner and csi-node-driver

[Maleware]

Description

As of the update for the mirror action stackabletech/docker-images#738 path are going to change in order to automate upload of dependencies to Nexus and Harbor

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

Beta Give feedback

1. Changes are OpenShift compatible
2. CRD changes approved
3. CRD documentation for all fields, following the style guide.
4. Helm chart can be installed and deployed operator works
5. Integration tests passed (for non trivial changes)
6. Changes need to be "offline" compatible

Reviewer

Beta Give feedback

1. Code contains useful comments
2. Code contains useful logging statements
3. (Integration-)Test cases added
4. Documentation added or updated. Follows the style guide.
5. Changelog updated
6. Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

Beta Give feedback

1. Feature Tracker has been updated
2. Proper release label has been added
3. Roadmap has been updated

[razvan]

This is a new major version. Did you research if it's backwards compatible with the previous one?

[lfrancke]

https://github.com/kubernetes-csi/external-provisioner/blob/v5.0.1/CHANGELOG/CHANGELOG-5.0.md

The external-provisioner now needs permissions to patch persistentvolumes. Please update your RBACs appropriately.

I have no idea if we use/need that. But it does not seem like a straightforward upgrade at least.

[nightkr]

Looking at the PR it came from (kubernetes-csi/external-provisioner#1155): yes we do need the permission, no it doesn't look like we have take the permission already.

[Maleware]

Yes, I'm updating it atm. I made another PR which was not the smartest thing. Put those together in this one now

[Maleware]

I've installed the end-to-end-security demo and updated both csi components to their new corresponding versions. I didn't see any pvc's to be deleted or rolled out again nor were any problems in the communication of the tools.

However, I would like @nightkr to have a last look before this get's putted into the release.

[Maleware]

Integration test: https://testing.stackable.tech/view/02%20Operator%20Tests%20(custom)/job/secret-operator-it-custom/3/

[Maleware]

Tests failed on hyperscaler, where all right locally:

--- PASS: kuttl (121.21s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/kerberos_krb5-1.21.1_openshift-false (62.93s)
        --- PASS: kuttl/harness/tls_openshift-false (23.70s)
        --- PASS: kuttl/harness/listener_openshift-false (34.55s)
PASS

[Maleware]

We're waiting on the tests for OpenShift before we merge it. Going to be done by @adwk67

[adwk67]

🟢 secret-operator tests on OKD with helm:

--- PASS: kuttl (121.91s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/tls_openshift-true (70.74s)
        --- PASS: kuttl/harness/listener_openshift-true (84.08s)
        --- PASS: kuttl/harness/kerberos_krb5-1.21.1_openshift-true (42.06s)
PASS

🟢 secret-operator tests on OKD with OLM bundles and updated CSDI versions:

--- PASS: kuttl (95.14s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/kerberos_krb5-1.21.1_openshift-true (29.02s)
        --- PASS: kuttl/harness/tls_openshift-true (52.01s)
        --- PASS: kuttl/harness/listener_openshift-true (55.50s)
PASS

🟢 hdfs-operator test on OKD with OLM bundles and updated CSDI versions:

--- PASS: kuttl (1013.60s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/kerberos_hadoop-latest-3.3.6_zookeeper-latest-3.9.2_krb5-1.21.1_kerberos-realm-PROD.MYCORP_kerberos-backend-mit_openshift-true (1003.10s)
PASS