Making GCPManagedCluster.Network a required field

[tasdikrahman]

/kind bug

What steps did you take and what happened:

As noted in this issue #1187 here, the Network field is a required field implicitly, as during the reconcile process of GCPManagedCluster, requires the presence of this field.

What we could potentially do here based on this discussion #1259 (comment) is to make it a required field either in v1beta1 or v1beta2

What did you expect to happen:
GCPManagedCluster.Network becomes a required field.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

reference PR which fixes the controller crashing. #1259

Environment:

• Cluster-api version:
• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[tasdikrahman]

/assign

[tasdikrahman]

potentially could be added as part of v1beta2 #1287

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten