✨ feat: Support ignition format (e.g. for Flatcar Linux)#797
✨ feat: Support ignition format (e.g. for Flatcar Linux)#797hajowieland wants to merge 2 commits into
Conversation
|
Your PR drops the Outscale section from UserData. Without it, public IPs and placement constraints do not work. The Outscale section is already stripped from UserData by the API on Vm creation, and querying the metadata for it should return a clean ignition config. Have you tested deploying flatcar without these changes ? I fail to see what would prevent ignition from working... |
|
Thanks @jfbus for the quick reply and yes, you're absolutely right, the change is not required. Sorry for wasting your time here - if you ever find yourself in Munich, let me know and I'll buy you a beer 🍺 For other users as a reference: If you want to use Flatcar, you need to enable the ignition format and also set the hostname via metadata service in the KubeadmConfigTemplate: spec:
template:
spec:
format: ignition
preKubeadmCommands:
- until HN=$(curl -fsS http://169.254.169.254/latest/meta-data/local-hostname); do sleep 2; done && hostnamectl set-hostname "$HN"KubeadmControlPlaneTemplate: spec:
template:
spec:
kubeadmConfigSpec:
format: ignition
preKubeadmCommands:
- until HN=$(curl -fsS http://169.254.169.254/latest/meta-data/local-hostname); do sleep 2; done && hostnamectl set-hostname "$HN" |
|
Thanks for the invitation ! Never been to Munich... I don't consider this a wasted time - it allowed me to learn a few things on Flatcar. I wished I had time to work on it... |
Description
This change adds support for the Ignition format used by Flatcar Linux.
Type of Change
Please check the relevant option(s):
How Has This Been Tested?
Please describe the test strategy:
Checklist
Additional Context
I also added support in image-builder to support building Flatcar images on Outscale (optionally with NVIDIA GPU support): kubernetes-sigs/image-builder#1986