We should at least investigate this, because we thought we handled the deprecation of v1beta1 => v1. It may be a case of 'compat' mode that got triggered because of something in the pod spec, or it may be that we just missed fixing this one.
We should at least investigate this, because we thought we handled the deprecation of v1beta1 => v1. It may be a case of 'compat' mode that got triggered because of something in the pod spec, or it may be that we just missed fixing this one.