Kubernetes Driver: switch to 'StatefulSet' from 'Deployment'

[ArielLahiany]

I've switched the Kubernetes driver object to 'StatefulSet' from 'Deployment' In order to support long-living persistent data directories between restart, and to meet the needs of the following issue: #2056
Please let me know if there are any other changes that are required, or if a different PR format is required.
Thank you.

[AkihiroSuda]

• new driver: kubernetes #167 (comment)

I avoided using StatefulSet because creating StatefulSet pods was quite slow at that time due to non-parallelizability.
Has the situation changed?

[AkihiroSuda]

podManagementPolicy should be set to Parallel

[AkihiroSuda]

Also please make sure to measure the startup time of the pods with a good number of replicas (around 5-10?), and there is no significant delay compared to Deployment

[ArielLahiany]

@AkihiroSuda
I've tested that logic on a freshly-installed vanilla K3s and everything seems to work as required.
I believe that the PR is failing duo to way that the GitHub Action is deploying the cluster.
How can we processed and move that PR along?

[AkihiroSuda]

ERROR: expected 1 replicas to be ready, got 0

Needs kubectl get pod -o yaml and kubectl logs for further analysis