Skip to content
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

[RFE] Add ignition support in kops #1029

Open
gabriel-samfira opened this issue May 18, 2023 · 4 comments
Open

[RFE] Add ignition support in kops #1029

gabriel-samfira opened this issue May 18, 2023 · 4 comments
Assignees
Labels
kind/feature A feature request

Comments

@gabriel-samfira
Copy link
Member

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.

@gabriel-samfira gabriel-samfira added the kind/feature A feature request label May 18, 2023
@gabriel-samfira
Copy link
Member Author

Cross link to the kops feature request: kubernetes/kops#15428

@gabriel-samfira
Copy link
Member Author

Issue that prompted this RFE: kubernetes/kops#15385

@andy-v-h
Copy link

It's possible to use cloudinit, the packet cloud image has cloud init enabled. I understand cloud-init and ignition are not feature compatiable, but it may be easier to get a cloud-init enable flatcar image running than support for ignition in an EC2 env

@gabriel-samfira
Copy link
Member Author

cloud-config already works by using coreos-cloudinit. As stated, getting kops to work with flatcar already has PRs proposed. The point of adding ignition support in kops is to allow flatcar as well as other distributions that use ignition exclusively, to work with kops.

This preference was expressed here: kubernetes/kops#15385 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request
Projects
Development

No branches or pull requests

2 participants