> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nvcf/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nvcf/_mcp/server.

# NVCF Self-Hosted 0.6.1 Release Notes

NVCF Self-Hosted 0.6.1 is a maintenance release. It replaces the archived
Bitnami Cassandra runtime with the official Apache Cassandra 5.0.8 image and an
in-house Cassandra Helm chart, removing the CVE-affected Bitnami runtime and its
bundled components. Behavior is otherwise equivalent: authentication, seed
discovery, metrics, schema initialization, and migrations are preserved.

## Highlights

| Change | Status | Summary |
| --- | --- | --- |
| Cassandra off Bitnami | GA | Cassandra runs on the official Apache Cassandra 5.0.8 image, deployed by an in-house Helm chart, replacing the Bitnami image and subchart. |

## Cassandra runtime and chart

The Cassandra runtime image is now built on the official Apache Cassandra 5.0.8
image instead of the archived Bitnami image, and the Bitnami Cassandra Helm
subchart is replaced by an in-house StatefulSet chart. This removes the
CVE-affected Bitnami base and its bundled components while keeping the same
operational surface: PasswordAuthenticator and CassandraAuthorizer, stable-DNS
seed discovery, the Prometheus metrics exporter, keyspace initialization, and
schema migrations.

The chart runs the nodes with `storage_compatibility_mode: NONE` to match the
existing fleet's on-disk and streaming format.

## Upgrade Notes

Fresh installs need no special handling; Cassandra comes up on the official
image with the in-house chart.

Existing clusters that already hold data need a migration, because the runtime
image, the Helm chart shape, and the on-disk data layout all change. A normal
in-place Helm upgrade does not carry an existing Bitnami-based cluster onto the
new stack. Follow the
[0.6.0 to 0.6.1 Upgrade](/nvcf/dev/0-6-0-to-0-6-1-upgrade) procedure, which describes
the supported migration methods (datacenter expansion, in-place volume
adoption, backup and restore) and their trade-offs.