-
Notifications
You must be signed in to change notification settings - Fork 45
Description
Current situation
When deploying a Kubernetes cluster using kops, flatcar needs to leverage coreos-cloudinit to complete the setup process. Currently kops does not support ignition.
Impact
We need to use coreos-cloudinit to support deployments of k8s via kops.
Ideal future situation
Ignition support is added in kops, and valid ignition userdata is generated when deploying distributions that leverage ignition.
Implementation options
It would be great if we had an extra flag in kops, or a config option that would prompt kops to generate proper ignition userdata when deploying a cluster.
Additional information
There are currently a number of PRs created against coreos-cloudinit, flatcar scripts repo and afterburn that enable kops clusters on flatcar without changes to kops.
The PRs are available at:
- Add multipart mime support and refactor coreos-cloudinit#21
- Detect multipart mime and ignore it scripts#823
- Write short form hostname coreos/afterburn#922
This fixes the issue for Flatcar, but we use a customized version of ignition that ignores non-ignition user-data and allows coreos-cloudinit to handle it later on. Distributions that do not ship the Flatcar customizations will simply err out with kops.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status