Releases: warm-metal/container-image-csi-driver
Releases · warm-metal/container-image-csi-driver
v0.8.2
What's Changed
- feat: Build and push docker images via GitHub Actions by @mbtamuli in #88
- fix: Broken workflow for pushing images by @mbtamuli in #89
- fix: single PV mounted on multiple pods as read-only erroring by @vadasambar in #99
New Contributors
Full Changelog: v0.8.1...v0.8.2
v0.8.1
Support for async image pull and mount
What's Changed
- feat: async image pull and mount by @vadasambar in #71
- Update Chart.yaml and Makefile to v0.8.0 by @mugdha-adhav in #82
Full Changelog: v0.7.0...v0.8.0
Dynamic volume provisioning support
What's Changed
- use correct path for serviceAccount secret by @MaxFedotov in #59
- Dynamic Volume Provisioning by @MaxFedotov in #57
- fix failed test cases by @kitt1987 in #63
- use IsMountPoint function from k8s.io/mount-utils to check if TargetPath is a mount point by @MaxFedotov in #66
- fix: unable to pull images from private ECR by @vadasambar in #67
- Update Chart.yaml version to v0.7.0 by @mugdha-adhav in #75
New Contributors
- @MaxFedotov made their first contribution in #59
Full Changelog: v0.6.1...v0.7.0
v0.6.4
What's Changed
- fix: v0.6.x remove node driver registrar lifecycle hook by @vadasambar in #72
- Release 0.6.4 by @mugdha-adhav in #73
New Contributors
- @mugdha-adhav made their first contribution in #73
Full Changelog: v0.6.3...v0.6.4
v0.6.3
v0.6.1
v0.6.0
v0.5.1
docker pull warmmetal/csi-image:v0.5.1
Breaking Changes
- VolumeAttributes.secret is replaced by
nodePublishSecretRef
, - Pulling private images using the ImagePullSecrets which attached to workload service accounts is no longer supported for security reasons. #29,
- The installation manifests are changed. Users should apply the new installation manifests to upgrade. I recommend our new utility
warm-metal-csi-image-install
#30.
Cri-o
- The project has been refactored, but no breaking changes are introduced.
- The installation manifest is changed, that is, the leading
unix
of the CRI endpoint URL is replaced bycontainerd
, orcri-o
to indicate different container runtime. And, a new flag--runtime-addr
is introduced for the CRI endpoint. The old--containerd-addr
is marked deprecated, but still available for containerd.