Kubernetes Resource Model - What Changes Would You Make?

As a developer advocate, your job is to sort of be a proxy for like the users and the community. I would probably create stronger patterns around who and when do these different sections get edited? We didn't have a good sense of the diversity of actors on these objects when we were first doing Kubernetes. There's a lot of backward compatibility concerns that make it a little bit more obtuse than I think anybody would really like.