What problem are you facing?

cluster-api-provider-gcp exposes a GCPCluster type and controller that does most of the setup around provisioning a Kubernetes cluster on GCP other than creating the actual compute instances. Under the hood the GCPCluster controller creates a number resources on GCP, some of which are already supported by provider-gcp. Supporting all of the resources would allow for an XRD to replicate the GCPCluster type and be serviced by a Composition with all of the required resources.

xref kubernetes-sigs/cluster-api#4095

How could Crossplane help solve your problem?

This list was generated on this CrossHack livestream.

Add support for the following resources:

• Network
• Router
  • References Network (source)
  • Embedded RouterNat
• GlobalAddress
• HealthCheck
  • Patches loadBalancerBackendPort (source)
• BackendService
  • References HealthCheckService (source)
  • References InstanceGroup (source)
• TargetTcpProxy
  • References BackendService (source)
• ForwardingRule
  • References GlobalAddress (source)
  • References TargetTcpProxy (source)
  • Patches LoadBalancerForwardingPort CAPI Cluster type
• InstanceGroup
  • References Network
  • Patches loadBalancerBackendPort --> groups instances for load balancing (source)
  • Potentially not needed for GCPCluster type (but is for GCPMachine)
• Firewall
  • References Network
  • Patches loadBalancerBackendPort --> Allow health checks firewall rule (source)