While testing we discovered that if the Storage Account token's token is refreshed Crossplane starts getting access errors until we restart the container.
How can we reproduce it?
Configured Crossplane to use a managed Identity to create the Storage Account. When the Storage Account token is automatically refreshed or force it to refresh. The previously working container stops working and will not recover.
What happened?
While testing we discovered that if the Storage Account token's token is refreshed Crossplane starts getting access errors until we restart the container.
How can we reproduce it?
Configured Crossplane to use a managed Identity to create the Storage Account. When the Storage Account token is automatically refreshed or force it to refresh. The previously working container stops working and will not recover.
What environment did it happen in?
Crossplane version: 1.8.0 crossplane/provider-jet-azure-controller:v0.10.0 crossplane/provider-jet-azure:v0.10.0
We are deployed on AKS and have tried various version from 1.21.x up with the same result.