Replacing Terraform to Linode CAPI provider

[mhmxs]

General:

• Have you removed all sensitive information, including but not limited to access keys and passwords?
• Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

---

Feature Requests:

• Have you explained your rationale for why this feature is needed?
• Have you offered a proposed implementation/solution?

---

Bug Reporting

Linode Terraform provider would be deprecated if not already has been. Would be nice to replace it to an uptodate solution. Linode CAPI provider would be a good choice. For more information, please follow the corresponding discussion here: linode/cluster-api-provider-linode#6

Expected Behavior

Replace cluser management scripts with Kubernetes Golang client calls:

linode-cloud-controller-manager/e2e/test/framework/cluster.go

Line 4 in 5572272

return RunScript("create_cluster.sh", ApiToken, cluster, Image, k8s_version, region)

• Start CAPI provider with it's dependencies.
• Execute tests
• Tear down test environment
• Upload logs to github

Regarding to CAPI provisioning I think speed is the main factor, because we would like to test project on CI. I think a full featured Kubernetes environment is a bit overkill for this task. So my suggestion is to spinning up a lightweight Kcp control plane and the capi provider(s) via Docker compose. Plain, old, boring but fast!

---

For general help or discussion, join the Kubernetes Slack team channel #linode. To sign up, use the Kubernetes Slack inviter.

The Linode Community is a great place to get additional support.