eriksjolund
December 2, 2022, 10:04am
#1
I noticed that Ignition support was added to cluster-api-provider-vsphere in
kubernetes-sigs:main ← johananl:johananl/ignition
opened 05:26PM - 10 Feb 22 UTC
**What this PR does / why we need it**:
This PR adds Ignition support to CAPV… and implements the first workload cluster flavor which uses Ignition based on Flatcar Container Linux.
Supersedes #1093.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #1006
**Special notes for your reviewer**:
TODO:
- [x] Update to latest API version?
- [x] Add Ignition flavor?
- [x] Add/update e2e tests
- [x] Figure out how to specify Flatcar image version in CI
- [x] Push Flatcar e2e image to test infra
- [x] Once https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/1618 is merged, run `make generate` and commit the new generated template
- [ ] ~Add a feature gate?~
- [x] Document usage
- [x] Remove TMP commits
- [x] Squash commits
**Release note**:
<!-- Write your release note:
1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
2. If no release note is required, just write "NONE".
-->
```release-note
Add support for Ignition bootstrap and add a Flatcar-based cluster flavor.
```
Do you know if it is possible to deploy Fedora CoreOS via cluster-api-provider-vsphere?
Any tips are welcome. In any case I will do some attempts to try it out myself.
jlebon
December 5, 2022, 7:28pm
#2
Nice find! I’m not aware of anyone having tried it yet with FCOS. The docs added there seem to imply it should be generic over any Ignition-based distro, so definitely worth a try. Please report back with your results!
But it’s worth noting also that the machine-api-operator in OKD and OCP I think already support cluster APIs for vSphere, including e.g. autoscaling workers. I found these docs for OKD.