Skip to content

Remove cloud provider node patch logic, remove BootstrapSucceeded condition from LXCMachine #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 22, 2025

Conversation

neoaggelos
Copy link
Contributor

@neoaggelos neoaggelos commented Apr 18, 2025

Summary

  • Do not configure spec.providerID in the provider code, this is now configured as part of the cluster template through the provider-id: "{{ v1.local_hostname }}" extra kubelet arg
  • Do not set the BootstrapSucceeded condition, as it is not required as part of the Infrastructure Provider contract. InstanceProvisioned and Ready conditions are enough

Changes

  • Cleanup API definitions
  • Mark lxcCluster.spec.skipCloudProviderNodePatch field as deprecated
  • Do not instantiate a ClusterCache, as we do not have to interact with the workload cluster directly

Notes

An important behavior change as part of this PR is that the provider no longer requires an active Incus agent running on VM instances (not important for containers. This also helps address some of the flakiness of the QuickStart KVM e2e tests in our CI environment

- Remove the BootstrapSucceeded condition from API
- Remove the internal/cloudinit package
- Remove the incus.GetCloudInitStatus() helper

Signed-off-by: Angelos Kolaitis <[email protected]>
- Do not set providerID from the provider side
- Mark lxcCluster.spec.skipCloudProviderNodePatch as deprecated in API
- Drop internal/cloudprovider package
- Set provider-id as kubelet extra args instead

Signed-off-by: Angelos Kolaitis <[email protected]>
@neoaggelos neoaggelos requested a review from a team as a code owner April 18, 2025 15:18
@neoaggelos neoaggelos merged commit f2c024c into lxc:main Apr 22, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant