K8s 1.16 - api changes

Looks like 1.16 will require a lot of our objects to be updated. For example, ingress needs to be networking.k8s.io/v1beta1, and deployments will be at apps/v1.

I am on Rancher 2.3.2 and 1.14 now. when i attempt to create an ingress by importing YAML where apiVersion: networking.k8s.io/v1beta1, the ingress gets created but the apiVersion appears to be reverted to extensions/v1beta1

So my question - what is the process for upgrading K8s to 1.16 with Rancher? Is this going to be a painful process? What is the best practice for updating all our our deployments and ingresses to the new api location?

Interesting - if I look at deployments (View YAML) in the Rancher GUI, they all show apps/v1. If i view same deployment with kubectl, it returns extensions/v1beta1

Why is this?