Currently, as part of the release process, one of the steps after a Go/No-Go decision is made is to create and publish the Flatcar SIG images and the Flatcar CAPI SIG images for the Stable channel for each current version of Kubernetes. This particular step is quite time-consuming, requiring approximately 30-45 minutes for each Kubernetes version. As a result, the entire process takes about 3-4 hours, possibly even longer.
Throughout this time-frame, the release manager must closely monitor the progress of the process to ensure that all steps are successfully executed.
Impact
This impacts the overall mental burden on the release manager, and is a bit error prone.
Ideal future situation
The build process of the image is integrated in the process after the VHDs are generated, and after the Go/No-Go we publish the final images through the release job
dongsupark
commented
11 months ago
Current situation
Currently, as part of the release process, one of the steps after a Go/No-Go decision is made is to create and publish the Flatcar SIG images and the Flatcar CAPI SIG images for the Stable channel for each current version of Kubernetes. This particular step is quite time-consuming, requiring approximately 30-45 minutes for each Kubernetes version. As a result, the entire process takes about 3-4 hours, possibly even longer.
Throughout this time-frame, the release manager must closely monitor the progress of the process to ensure that all steps are successfully executed.
Impact
This impacts the overall mental burden on the release manager, and is a bit error prone.
Ideal future situation
The build process of the image is integrated in the process after the VHDs are generated, and after the Go/No-Go we publish the final images through the release job
cc @invidian @pothos