v0.8.4

What's Changed

• internal/driver: Rename and export the driver name by @nesv in #185
• internal/driver: Controller cleanup by @nesv in #186
• add codecov reporting by @eljohnson92 in #187
• [Fix] Setting the correct image tag for CSI E2E test image on main branch by @komer3 in #189
• go.mod: Update github.com/container-storage-interface/spec to v1.10.0 by @nesv in #190
• Add LUKS e2e test by @komer3 in #192
• [Clean Up] - NodeStageVolume, NodeUnStageVolume, Adding golangci lint to GHA, and various small cleans by @komer3 in #191
• [Clean Up] updating the k8s mounting pkg to latest supported one by @komer3 in #193
• [Clean Up] remove unused vars by @komer3 in #194
• [fix] Address the errors we are seeing for NodeExpandVolume() in CSI-Sanity test by @komer3 in #196
• [Feat] Adding CSI Sanity tests to GHA by @komer3 in #195
• [feat] : add support to run upstream k8s e2e tests by @rahulait in #197
• add xfsprogs to add mkfs.xfs binary to csi-linode-node pod by @rahulait in #199
• [Fixes] - Addressing test cases we found running sanity tests for Controller Plugin by @komer3 in #198
• [Fix] Re-enable Readonly since we support mounting the volume in that mode on the Node Plugin side by @komer3 in #201
• [Fix] Update Linode Token to correct one in GHA by @komer3 in #203
• Adding e2e test to verify ReadOnly volumes are mounted by Node plugin by @komer3 in #202
• [Clean-Up] Refactor NodeUnpublishVolume() by @komer3 in #200
• [Cleanup] Nodepublishvolume() refactor by @komer3 in #204
• [Cleanup] Pull all the test related files and folders under 'tests' directory by @komer3 in #207
• [Cleanup] Replace Status.Error() with helper func() defined in errors.go by @komer3 in #209
• [Cleanup] Move the fake test helper code into faketestutils package by @komer3 in #208
• test ext2, ext3, ext4, xfs as supported filesystem type by @rahulait in #206
• [Cleanup] refactor the utils and common pkgs by @amold1 in #212
• [Cleanup] Refactor LinodeIdentityServer for uniformity by @komer3 in #211
• [Cleanup] Refactor LinodeNodeServer for consistency by @komer3 in #210

New Contributors

• @rahulait made their first contribution in #197
• @amold1 made their first contribution in #212

Full Changelog: v0.8.3...v0.8.4

helm-v0.8.4

The Container Storage Interface (CSI) Driver for Linode Block Storage enables container orchestrators such as Kubernetes to manage the life-cycle of persistant storage claims.

v0.8.3

What's Changed

• ⭐ E2E tests using Chainsaw by @komer3 in #178
• 🐛 internal/driver: Fix off-by-one error with max volume attachments by @nesv in #184

Full Changelog: v0.8.2...v0.8.3

helm-v0.8.3

The Container Storage Interface (CSI) Driver for Linode Block Storage enables container orchestrators such as Kubernetes to manage the life-cycle of persistant storage claims.

v0.8.2

What's Changed

• Fix release process - change paths to manifests by @tchinmai7 in #180

Full Changelog: v0.8.1...v0.8.2

v0.8.1

What's Changed

⚠️ Do not use this version. The CI process had a bug, and didn't actually build and publish images. Use v0.8.2 instead which includes all these changes.

Bug fixes

• Fix script to look at just the id by @tchinmai7 in #179

Other changes

• Polish create cluster script by @mhmxs in #166
• Rename "pkg/linode-bs" to "internal/driver" by @nesv in #172
• Update go version to 1.22 and linodego to 1.35 by @komer3 in #173
• Add a CODEOWNERS file by @nesv in #174
• Adding GHCR image build-push support by @komer3 in #175
• trigger helm-release off of release tags instead of the main branch by @eljohnson92 in #176
• internal/driver: Simplify set up of driver capabilities by @nesv in #177

Full Changelog: v0.8.0...v0.8.1

helm-v0.8.2

The Container Storage Interface (CSI) Driver for Linode Block Storage enables container orchestrators such as Kubernetes to manage the life-cycle of persistant storage claims.

helm-v0.8.1

The Container Storage Interface (CSI) Driver for Linode Block Storage enables container orchestrators such as Kubernetes to manage the life-cycle of persistant storage claims.

v0.8.0

This release contains #170 which is a breaking change, as it contains changes to how the CSI driver is configured. Please see that pull request for details.

What's Changed

• Remove "pkg/linode-bs/metadata" by @nesv in #169
• Add golangci-lint configuration by @nesv in #171
• Configure the CSI driver through environment variables by @nesv in #170

Full Changelog: v0.7.0...v0.8.0

v0.7.0

What's Changed

• feat: Allow more than 8 volume attachments for larger Linode instances (#167)

Up to 64 volume attachments for larger Linode instances

On Linode instances with 16GB of RAM or more, the number of block storage volumes that can be attached to a Linode instance has increased! The following table shows the maximum number of volume and disk attachments for "standard" Linode instances:

Instance Type	Memory/RAM	Max. Volume + Disk Attachments
g6-nanode-1	1GB	8
g6-standard-1	2GB	8
g6-standard-2	4GB	8
g6-standard-4	8GB	8
g6-standard-6	16GB	16
g6-standard-8	32GB	32
g6-standard-16	64GB	64
g6-standard-20	96GB	64
g6-standard-24	128GB	64
g6-standard-32	192GB	64

On a node with 16GB of RAM, a total of 16 volumes can be attached; on a node with 32GB of RAM, 32 volumes; etc. No more than 64 volumes can be attached to a node. This limit is currently set by Linode's internal virtualization stack, and is enforced by the CSI driver. The number of attached volumes is a combination of block storage volumes and "instance disks" (e.g. the boot disk). As the maximum number of attachments follows the amount of memory allocated for an instance, this scheme also applies to dedicated, premium, gpu, and highmem instance classes.

In order to support this change, block storage volume attachments are no longer persisted across reboots. By persisting the volume attachments (the default behaviour in the Linode API), the maximum number of attachable volumes and instance disks is 8, since those attachments are added to an instance's configuration profile.

New Contributors

• @nesv made their first contribution in #167