feat: Introduce a stage after node has joined the p2p cluster

[6ixfalls]

Is your feature request related to a problem? Please describe.

Currently its difficult to apply manifests after the k3s server has started while in p2p mode. When I use k3s blocks, I'm able to do this during the boot stage, but with p2p enabled, there's no stage that runs after p2p has negotiated the cluster roles. As a result, I'm forced to use reconcile for this, but that's not a reliable solution because if the cluster takes more than 5 minutes to bootstrap, it takes an additional 60 minutes before my manifests and scripts are run and therefore leads to a poor user experience.

Describe the solution you'd like

There should be another kairos agent stage, something like cluster-ready, which is called when the current node has received a p2p role and after the k3s server or agent is started.

Describe alternatives you've considered

I've tried the reconcile stage but it will take 65 minutes after first boot before the cluster is ready.

[ci-robbot]

Hello,

This is a bot, an experiment of @mudler and @jimmykarily. Thank you for opening the issue #2518 in the repository kairos-io/kairos.

Your issue seems to meet most of the project's requirements. There's a clear description of the problem and the desired solution. You have also provided an alternative solution considered.

However, it would be helpful if you could specify which versions of the relevant artifacts you are using. This information can help the maintainers better understand and address the issue.

Current labels: [triage]

[jimmykarily]

The provider-kairos already runs some stages. There is no reason why we couldn't introduce another one.

[mudler]

The provider-kairos already runs some stages. There is no reason why we couldn't introduce another one.

indeed, I think it's just about documentation, there are already two stages being fired from the provider:

• provider-kairos.bootstrap.before.<role> https://github.com/kairos-io/provider-kairos/blob/ca56b8f4ab7778b14037fcc4c45f6f2ebed155f9/internal/role/p2p/master.go#L165
• provider-kairos.bootstrap.after.<role> https://github.com/kairos-io/provider-kairos/blob/ca56b8f4ab7778b14037fcc4c45f6f2ebed155f9/internal/role/p2p/master.go#L225

@6ixfalls are those enough for your use case? it is more complex to determine when the cluster is ready after all nodes have joined the p2p network - which likely would require a larger work.

[6ixfalls]

That is actually exactly what I'm looking for - definitely documentation is important because I had no idea those existed 😅