jiva-operator VS dynamic-localpv-provisioner

OpenEBS Jiva (declared stable), has added support for a CSI Driver and Jiva operator that include features like:

# gha-runner-scale-set-value.yml githubConfigUrl: "https://github.com/myorg/myrepo" githubConfigSecret: github_token: "my-PAT" ## maxRunners is the max number of runners the autoscaling runner set will scale up to. maxRunners: 5 ## minRunners is the min number of idle runners. The target number of runners created will be ## calculated as a sum of minRunners and the number of jobs assigned to the scale set. minRunners: 1 containerMode: type: "kubernetes" ## type can be set to dind or kubernetes ## the following is required when containerMode.type=kubernetes kubernetesModeWorkVolumeClaim: accessModes: ["ReadWriteOnce"] # For local testing, use https://github.com/openebs/dynamic-localpv-provisioner/blob/develop/docs/quickstart.md to provide dynamic provision volume with storageClassName: openebs-hostpath storageClassName: "managed-csi" resources: requests: storage: 2Gi template: spec: securityContext: fsGroup: 123 ## needed to resolve permission issues with mounted volume. https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors#error-access-to-the-path-homerunner_work_tool-is-denied containers: - name: runner image: ghcr.io/actions/actions-runner:latest command: ["/home/runner/run.sh"] env: - name: ACTIONS_RUNNER_REQUIRE_JOB_CONTAINER value: "false" ## To allow jobs without a job container to run, set ACTIONS_RUNNER_REQUIRE_JOB_CONTAINER to false on your runner container. This instructs the runner to disable this check. volumes: - name: work ephemeral: volumeClaimTemplate: spec: accessModes: [ "ReadWriteOnce" ] storageClassName: "managed-csi" resources: requests: storage: 2Gi

Ahhhh So your'e using openebs localpv (openebs/dynamic-localpv-provisioner?). Yeah I couldn't go with that since it didn't properly limit space, but if you're running the DBs then you have controls of that stuff at a higher level (and it's probably good to not be too strict to not hurt user workloads). XFS supposedly does the limiting if you set up the underlying storage properly now but I couldn't get it to work.

OpenEBS Hostpath LocalPV (declared stable), the first and the most widely used LocalPV now supports enforcing XFS quotas and the ability to use a custom node label for node affinity (instead of the default 'kubernetes.io/hostname').