flow-modules
and functions
in your Helm chart file. If you find them, you need to migrate to the current NFS structure.
Prerequisites
- Cognigy.AI 4.90 or later.
- The
kubectl
utility is installed locally on a Linux or MacOS client host. Windows client hosts aren’t supported. - Helm 3.9 or later installed on the client host.
- Kubernetes cluster meets general Cognigy.AI prerequisites, including hardware resources.
- Runtime and IDE file shares have been deployed.
Migration Process
To migrate to the current NFS structure, you need to:- Adjust feature flags to handle multiple NFS shares during the migration process from the old to the current NFS structure.
- Run the migration job to copy the data from the old NFS structure into the current NFS structure.
- Clean up the old NFS structure.
Migration Steps
For this migration guide, consider the namespace ascognigy-ai
and the Helm chart file name as cognigy-ai-values.yaml
. You need to adjust the following instructions to match to your namespace and Helm chart file name.
Activate the NFS Restructuring Feature
-
In the
cognigy-ai-values.yaml
file, add the following sections at the root level: -
Deploy the Cognigy.AI Helm chart:
Finish Migration and Switch to New NFS Shares
After the migration job is completed and all resources are located in the new NFS shares, follow these steps:-
Update the
cognigy-ai-values.yaml
file: -
Deploy the Cognigy.AI Helm chart:
Post-Migration Steps
SetmigrateFS.finished
to true
within seven days after the migration. This setting ensures the migration process is fully completed and stable before finalizing, and automatically deletes the storageClass
object in the Persistent Volume Claim of the old NFS shares. To clean up these NFS shares completely, proceed as follows:
-
In
cognigy-ai-values.yaml
, remove the trace offlow-modules
andfunctions
by deleting the following code: -
Delete all released volumes that were related to
flow-modules
andfunctions
.