Support multiple GKE configurations in GCPManagedControlPlane

[dantiandb]

/kind feature

Describe the solution you'd like CAPG should support the following features provided by GKE

• ClusterIpv4Cidr (as defined in containerpb.Cluster)
• AddonsConfig
  • DnsCacheConfig
  • GcePersistentDiskCsiDriverConfig
• ResourceLabels
• IPAllocationPolicy (as defined in containerpb.IPAllocationPolicy)
  • UseIpAliases
  • ClusterSecondaryRangeName
  • ServicesSecondaryRangeName
  • ClusterIpv4CidrBlock
  • ServicesIpv4CidrBlock
• MaintenancePolicy
• NetworkConfig (as defined in containerpb.NetworkConfig)
  • DnsConfig
  • DatapathProvider
• DefaultMaxPodsConstraint
• PrivateClusterConfig
• ShieldedNodes
• WorkloadIdentityConfig
• LoggingConfig

Anything else you would like to add: Feature support is scoped to what is supported by the GCP containerpb SDK https://pkg.go.dev/cloud.google.com/go/container/apiv1/containerpb

[dantiandb]

/assign dantiandb

[richardcase]

We also have an existing issue #906

[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

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.