Add build workflow for pull request Docker image

[hlts2]

WHAT

• Added build workflow for pull request docker image

WHY

Until now, builds were only done during release. To use Docker image with new features or changes for testing, we had to manually build them locally and upload them to the registry.
This process was time-consuming and made collaboration difficult for the team.

With this new CI workflow, Docker image for each pull request are automatically build and published. The image are updated whenever changes are made to the pull request, and the image tag follow pr-{number}. (Using pr-{number} instead of commit hashes helps avoid an excessive increase in tags, making management simpler and more efficient. ) This allows the team to test changes faster and more easily, improving efficiency and ensuring better quality before releases.

FYI

• The following is an uploaded docker images

  • https://hub.docker.com/layers/civo/csi/pr-32/images/sha256-87cb628afc9cbdce92cb0b3c1a6f9d74a5645f87829f5e3b184a54e9bee0a555?context=explore

• The following is the result of local envrionment

❯ docker run --rm civo/csi:pr-32 --version
Unable to find image 'civo/csi:pr-32' locally
pr-32: Pulling from civo/csi
da9db072f522: Already exists
646621e749e7: Pull complete
67802e5dc3f3: Pull complete
4f4fb700ef54: Pull complete
970685bff73b: Pull complete
Digest: sha256:176a9ed50251ff322b3804d16201b3ac969ffd94e6c8cbb697f4bb7adb10290f
Status: Downloaded newer image for civo/csi:pr-32
7:13AM INF CSI driver version=pr-32

[hlts2]

Note

For now, the workflow only uploads to Docker Hub. If uploading to Google Container Registry is also acceptable, it will added separately 💡

[rytswd]

LGTM, we can proceed with this, and adjust as necessary 👍
(We did discuss internally how we may want to tag with commit sha, but that can be later)