smuu

Consider combining of `Commit` and `Start`

2

Before working on this, please check if this even makes sense. Is it necessary to have `Commit` and `Start` separately? Could it be enough to have `Start`?

This way, you don't need to call `Destroy` on all Instances manually. Also, there is currently no way to delete the timeout handler. It will delete itself after the timeout...

!breaking change This is counterintuitive and could confuse. Also, cloning is allowed only in `Commited` state, where it could still be changed. Only allow those to use in `Preparing` state.

Use supported Kubernetes Version instead of latest

1

https://github.com/celestiaorg/knuu/blob/cb478fc1fb7786f527776aec4680cb8a30bf1abb/pkg/knuu/knuu.go#L92 Currently, the `latest` image is used, which could cause issues with compatibility. Instead, use an image with the supported Kubernetes version. Ref.: https://github.com/celestiaorg/knuu/issues/29

Do busy waiting in replacement with a timeout

1

- https://github.com/celestiaorg/knuu/blob/62170e970a1da935458910d8c9e74b5cd390e15e/pkg/k8s/k8s_statefulset.go#L74 - https://github.com/celestiaorg/knuu/blob/62170e970a1da935458910d8c9e74b5cd390e15e/pkg/k8s/k8s_pod.go#L104 - check for other places in the code

I expect it to fail

Interacting with the Instance should be only possible if the Instance is running.