Preparing for DataWalk on Containers

Version 5.1 is the last DataWalk release supporting non-containerized infrastructure and Coupled Storage (CS) mode. Support for all non-container deployments ends November 2027.

Summary

This notice updates the advisory sent in December 2025. If you have not started migration planning, now is the time.

Timeline

Now: Version 5.1 supports both container and non-container deployments. Last release for Coupled Storage (CS) mode.

Version 5.2 and beyond: All new releases require containers and Decoupled Storage (DS) mode.

November 2027: Support for non-container infrastructure ends.

Why containers

• Cost efficiency: elastic and scalable – resources match demand.
• Infrastructure optimization: shared OS and libraries, maximizing server density.
• Operational simplicity: standardized maintenance, consistent environments from development to production.

Required actions

1. Confirm your environment supports Decoupled Storage (DS).
2. Verify servers meet minimum OS requirements: RHEL 8.10 or Rocky 8. On a version prior to 4.5? Contact support for a sizing review.
3. Identify Kubernetes/container-trained administrators in your organization.

Public cloud customers (AWS, GCP, Azure) will find container infrastructure already available. Private cloud and on-premises customers should begin planning now.

More information

Preparing for DataWalk on containers:  https://customers.datawalk-support.com/en/support/solutions/articles/6000277656-preparing-for-datawalk-on-containers

Technical Migration Guide:  https://docs.datawalk.com/en:admin-guides:latest_release:install:k8s:migrate_from_vm_to_k8s:start?s[]=vm&s[]=k8s

Questions: support@datawalk.com