Skip to content

[RFE] Add ignition support in kops #1029

@gabriel-samfira

Description

@gabriel-samfira

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:

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

Labels

Type

No type

Projects

Status

🪵Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions