Unable to specify Maintenance Window and Maintenance Exclusions in GKE cluster

[Kun483]

/kind feature

Describe the solution you'd like
I think there is no evident place to specify Maintenance Window and Maintenance Exclusions.

I followed clusterctl guide to create a GKE cluster. Reference: https://cluster-api-gcp.sigs.k8s.io/topics/gke/creating-a-cluster.

kind create cluster
export EXP_CAPG_GKE=true
export EXP_MACHINE_POOL=true
clusterctl init --infrastructure gcp

Then I applied the cluster template from https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/v1.6.1/templates/cluster-template-gke.yaml.

What did you expect to happen:
I expect we to have the some options to set maintenancePolicy like startTime, endTime, and frequency.

Anything else you would like to add:

Environment

• Cluster-api version: v1.7.3
• CAPG version: v1.6.1
• Kubernetes version: (use kubectl version): Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.29.5-gke.1091000

[tasdikrahman]

/assign

[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