Initial analysis and planning for CAPI v1beta1 to v1beta2 migration

[Copilot]

The provider uses CAPI v1.11.5 but still imports v1beta1 types (Conditions, APIEndpoint, FailureDomains) that will be deprecated. This PR documents the migration scope.

Analysis Completed

API types using v1beta1.Conditions in Status:

• GCPManagedControlPlane, GCPManagedCluster, GCPManagedMachinePool (exp/api/v1beta1)
• GKEConfig (exp/bootstrap/gke/api/v1beta1)

API types using v1beta1 common types:

• APIEndpoint in Spec: GCPCluster, GCPManagedCluster, GCPManagedControlPlane
• FailureDomains in Status: GCPCluster, GCPManagedCluster
• ObjectMeta: GCPClusterTemplate

Code requiring updates:

• GetConditions/SetConditions methods (2 types)
• Condition type constants in conditions_consts.go
• Controllers: gcpcluster_controller.go, all exp/controllers
• Scopes: cluster, managedcluster, managedcontrolplane, managedmachinepool
• Services: container/clusters, container/nodepools

Migration Phases Identified

1. Update condition type constants from clusterv1beta1.ConditionType to clusterv1.ConditionType
2. Migrate Status.Conditions fields and GetConditions/SetConditions methods
3. Replace v1beta1.APIEndpoint, v1beta1.FailureDomains, v1beta1.ObjectMeta
4. Update controllers, scopes, and services to work with v1beta2 types
5. Validate with unit and integration tests

Implementation awaits confirmation on backward compatibility requirements and preferred change granularity.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cluster-api.sigs.k8s.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.