Current released image - ghcr.io/nexgencloud/csi-hyperstack/csi:v0.0.11
This documentation provides instructions for installing and using the Hyperstack CSI Driver. The CSI provisioner for hyerstack CSI driver is hyperstack.csi.nexgencloud.com.
Before you begin, ensure you have the following tools installed:
- Go 1.24
- Helm
- A Hyperstack Kubernetes cluster
-
(Optional) gRPCurl – Useful for debugging gRPC calls.
go install github.com/fullstorydev/grpcurl/cmd/grpcurl@latest
Run go mod tidy before starting the gRPC server:
go run main.go start \
--endpoint="unix://tmp/csi-hyperstack.sock" \
--hyperstack-api-address="<API_BASE_URL>" \
--hyperstack-api-key="<API_KEY>" \
--service-controller-enabled \
--service-node-enabledTo list the available gRPC calls:
grpcurl --plaintext unix:///tmp/csi-hyperstack.sock listYou can invoke a specific RPC method for a given operation using grpcurl.
To build the image locally:
make docker-build VERSION=<VERSION> # build only
make docker-build-push VERSION=<VERSION> # build and push to GHCRRefer to the charts/csi-hyperstack documentation for details on installation and usage with Helm.
Pushing a v*.*.* tag is the whole release. It runs .github/workflows/release.yml,
which builds the image and then publishes the chart.
git tag v0.0.12 origin/main
git push origin v0.0.12The tag is the single source of truth for both versions:
value for tag v0.0.12 |
|
|---|---|
| image | ghcr.io/nexgencloud/csi-hyperstack/csi:v0.0.12 |
chart version |
v0.0.12 |
chart appVersion |
v0.0.12 |
Chart.yaml is rewritten inside the workflow before packaging, so its committed
values are ignored — do not bump them by hand.
The chart job runs only after the image push succeeds, so a published chart can never point at an image that does not exist.
Charts are published as GitHub Releases tagged csi-hyperstack-<version>, with
the index committed to the gh-pages branch and served at
https://nexgencloud.github.io/csi-hyperstack.
Versions are compared with the leading v ignored, so each tag must sort above
the last released one — v0.0.7 would rank below the existing 0.0.10 and
never be served as latest.
For more information about the features of the Hyperstack API, visit the Hyperstack Documentation.
Relevant docs: