Using Terraform to manage an LKE cluster creates obstacles in configuration and state data persistence.
While this could be rectified by using an Object Storage backend, it may be more powerful to allow the cluster to manage its own state with Crossplane's Helm provider managing the workloads within that cluster. The definition of the cluster would be a Crossplane composition in this scenario. The cluster would be created through either Terraform or Crossplane.
The services within the cluster would be crossplane managed.
Could a secondary LKE cluster (with a single nanode or no nodes) be used as the data cluster?
Using Terraform to manage an LKE cluster creates obstacles in configuration and state data persistence. While this could be rectified by using an Object Storage backend, it may be more powerful to allow the cluster to manage its own state with Crossplane's Helm provider managing the workloads within that cluster. The definition of the cluster would be a Crossplane composition in this scenario. The cluster would be created through either Terraform or Crossplane. The services within the cluster would be crossplane managed.
Could a secondary LKE cluster (with a single nanode or no nodes) be used as the data cluster?