Feature flags are not processed when a velero sha256 image is used for velero install.

[poojitab]

Describe the bug

• When velero sha256 image is used for velero install by OADP operator 0.4.2, feature flags provided for this container are not captured. Hence "EnableLocalMode" is neither parsed/set in configMap 'velero-vsphere-plugin-feature-states' by vSphere plugin.
• Velero sha256 image used was: velero/velero@sha256:934dae8b2e17b4298bca95f45ec3620a283647297fb8ba8c0f5977e8238a97ee
• In this code (

  velero-plugin-for-vsphere/pkg/cmd/utils.go

  Line 89 in fb16664

  if containerName == container.Name && containerName == utils.GetComponentFromImage(container.Image, constants.ImageContainerComponent) {

  ) , Looks like container name "velero" is matched for while looking for feature flags whereas in the above case "velero@sha256" is received.
• Velero install command:
  • root@irv-vm-90-66:~# ./velero install --namespace velero-test --image "velero/velero@sha256:934dae8b2e17b4298bca95f45ec3620a283647297fb8ba8c0f5977e8238a97ee" --no-secret --no-default-backup-location --use-volume-snapshots=false --plugins vsphereveleroplugin/velero-plugin-for-vsphere:v1.3.0 --features EnableLocalMode

To Reproduce

• Set "EnableLocalMode" feature flag in velero deployment.
• Use velero sha256 image for velero install.

Expected behavior

• When velero sha256 image is used, feature flags should be processed as it was done before and corresponding value should be set in 'velero-vsphere-plugin-feature-states' configMap in velero namespace.