Set empty objects instead error on create

[rawmind0]

Issues rancher/rancher#32440 and rancher/rancher#32553

This PR contains a proposal to fix commented issues. The gke-operator is not distinguishing between nil objects and empty objects. For not required field, it should generate empty objects instead of returning an error if they are nil. This is affecting the use of rancher go cli as explained at related issues.

I've built a Rancher server using this patched gke-operator and the tests seems working fine using go cli and ui for imported and new gke clusters

[cmurphy]

@rmweir can you give your thoughts on this? Since this is strictly for creates I think it could work.

[cmurphy]

It doesn't address the core issue which is how norman handles empty fields

[rawmind0]

It doesn't address the core issue which is how norman handles empty fields

Agreed, Norman should generate same types at API and go cli. This is just proposed as alternative

[rmweir]

I'm not in favor of this fix. We should avoid writing to the spec, if we can as it should be driven by the user. We should take a deeper look at norman since I don't think this needs to be done for v2.5.8.

[rmweir]

An additional issue is that I don't think our integration implementation in rancher expects gke-operator to change the spec and would possible overwrite it unless we change code there.

[cmurphy]

We're going to move toward annotating the nullable fields with rancher/norman#400 to generate them as pointers in the client code, that way clients will be able to differentiate between nil and empty values and this won't be needed. Thank you!