I'm not aware of this problem, but maybe it was related with a Deployment specification that was written for the old Kubernetes version.

An article was just updated to comply with the newest Kubernetes version (1.23) so I hope your problem should disapear.

If it's still persist please let me know. Thanks!