[dev-v2.10] rancher-vsphere-csi 105.1.0+up3.3.1-rancher7 add

[pedromfcarvalho]

This incorporates this upstream change:

• feat(logging): add support for passing additional CSI container args vsphere-charts#96

Issue: rancher/rancher#48053

Engineeering testing

For testing that this latest bump had an effect, I installed the csi chart in the local cluster, even though it wasn't a vsphere cluster, because it was still possible to verify that arguments could be passed. To do this, I customized the following values before installing the chart (directly in the value yaml view):

csiController:
  csiResizer:
    enabled: true
  image:
    additionalArgs: ["-version"]
    csiAttacher:
      additionalArgs: ["--logging-format=json"]
    csiProvisioner:
      additionalArgs: ["--version"]
    csiResizer:
      additionalArgs: ["--logging-format=json"]
    csiSnapshotter:
      additionalArgs: ["-version"
    livenessProbe:
      additionalArgs: ["--logging-format=json"]
    vsphereSyncer:
      additionalArgs: ["-version"]

csiNode:
  image:
    additionalArgs: ["-version"]
    livenessProbe:
      additionalArgs: ["--logging-format=json"]
    nodeDriverRegistrar:
      additionalArgs: ["--logging-format=json"]

blockVolumeSnapshot:
  enabled: true

Note that these values have to be configured individually, and the other ones left as they are. The point is to pass additional args to every container. It's also necessary to enable the csi resizer and block volume snapshots so two of the containers run.

After this, I checked the logs every container for one controller deployment and the single node deployment (a total of 10 containers). Those that were passed --logging-format=json had json output in their logs, and those that were passed -version/--version printed their version before exiting. Most containers failed because this was not run in a vsphere environment, but it was sufficient to verify that the arguments were being passed correctly.

QA considerations

Test suggestions:

• The checks from engineering testing above, to verify the effects of this bump
• Any other usual vsphere CSI tests not specific to this bump to check for regressions

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.