This is a valid error. The resourceID and clientID are defined as an array {} in the output posted in the comment, but clientID and resourceID are of type string. If type upgrade fails for 1.6.0, then the MIC pod shouldn't start because 1.6.0 MIC will not work with the old AzureIdentity and AzureIdentityBinding with wrong case.
Most helpful comment
This is a valid error. The
resourceIDandclientIDare defined as an array{}in the output posted in the comment, butclientIDandresourceIDare of type string. If type upgrade fails for 1.6.0, then the MIC pod shouldn't start because 1.6.0 MIC will not work with the oldAzureIdentityandAzureIdentityBindingwith wrong case.