cluster-api-provider-ibmcloud icon indicating copy to clipboard operation
cluster-api-provider-ibmcloud copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Bootstrap cluster with ignition

Open mkumatag opened this issue 2 years ago • 19 comments

/kind feature /area provider/ibmcloud

Describe the solution you'd like https://cluster-api.sigs.k8s.io/tasks/experimental-features/ignition.html

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

mkumatag avatar Sep 09 '22 04:09 mkumatag

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 08 '22 04:12 k8s-triage-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 08 '23 05:03 k8s-triage-robot

/remove-lifecycle stale

mkumatag avatar Mar 08 '23 07:03 mkumatag

Fedora CoreOS is still pending for ppc64le, will explore this task once builds are available for the testing.

mkumatag avatar May 19 '23 05:05 mkumatag

/assign @Prajyot-Parab Update - Explore on booting Fedora CoreOS with ignition for CAPIBM PowerVS K8s cluster.

@mkumatag can you please add the reference links/urls for the Fedora CoreOS (ppc64le) builds.

Prajyot-Parab avatar Oct 19 '23 05:10 Prajyot-Parab

@Prajyot-Parab https://fedoraproject.org/coreos/download/?stream=stable&arch=ppc64le#download_section you can download ppc64le stable images from here.

yussufsh avatar Oct 22 '23 03:10 yussufsh

@Prajyot-Parab can you document the initial investigation you have done and move this work item to next release.

mkumatag avatar Dec 12 '23 14:12 mkumatag

/milestone Next

Prajyot-Parab avatar Dec 12 '23 16:12 Prajyot-Parab

The default configuration engine for bootstrapping workload cluster machines is cloud-init. Ignition is an alternative engine used by Linux distributions such as Flatcar Container Linux and Fedora CoreOS and therefore should be used when choosing an Ignition-based distribution as the underlying OS for workload clusters.

Note This initial implementation uses Ignition v2 and was tested with Flatcar Container Linux only. Future releases are expected to add Ignition v3 support and cover more Linux distributions.

@mkumatag as per my initial understanding we will need to build the flatcar stable image for powervs, once we have that we can try the already tested workflow using it.

Not sure how this is going to work with Fedora CoreOS-

  1. We will need some modifications on top of it to make it CAPIBM ready right? If yes, will this be somehow done as part of image builder process or it will be dealt with externally?

@mkumatag need your guidance on this one.

Prajyot-Parab avatar Jan 18 '24 10:01 Prajyot-Parab

Flatcar image is not available for the power, let's explore the experiment with the fedoracore image directly and see what kind of errors we are hitting while running the flow?!

mkumatag avatar Jan 18 '24 14:01 mkumatag

Summary - We explored with FerdoraCoreOS 39 for Power

  1. The version of ignition inside image is 2.17.0 => 3.x.x spec
  2. The created infra machine was able to fetch the ignition from mentioned URL.
  3. The issue is with config version mismatch while booting above machine via ignition. This is result of ignition file being generated using older spec 2.3.0.
  4. Ignition file is generated while upstream CAPI (which in-turn uses flatcar package), which supports only 2.3.0 and no 3.x.x specs.

This will possibly need more exploration and upstream CAPI contributions to add support for spec 3.x.x ignition versions.

Prajyot-Parab avatar Feb 08 '24 01:02 Prajyot-Parab

@Karthik-K-N feel free to add more info, if i missed anything.

Prajyot-Parab avatar Feb 08 '24 01:02 Prajyot-Parab

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar May 09 '24 04:05 k8s-triage-robot

/remove-lifecycle stale

mkumatag avatar May 09 '24 11:05 mkumatag

WIP PR is submitted https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/pull/1687, Need to complete it.

Karthik-K-N avatar May 09 '24 12:05 Karthik-K-N