Upgrading Satori

Satori provides you with the ability to upgrade and maintain your on-prem DAC deployment with ease.

Learn more about the Satori Data Platform and Schedule a demo meeting

You can download the latest version of the Satori DAC deployment package and choose from a number of available options. These options are divided into recommended versions and early bird beta versions.

Screenshot

Saving the Upgrade Mode Settings

The Satori upgrade mode is set to Manually Download and Upgrade by default. If you want to change the default upgrade setting you simply change the upgrade more by selecting one of the available options.

Manually Download and Upgrade
Upgrade Automatically
Deploy a Specific version

Once you have selected the relevant option from the drop menu ensure to first click the SAVE button to lock the upgrade mode.

Screenshot

DAC Package Upgrade Options

1 - Manually Downloading and Upgrading the DAC Version - To manually upgrade your DAC to the latest version perform the following steps:

Select the DAC's view for the Satori Settings.
Click on the name (link) of your DAC deployment in the table provided.
Select the Upgrade Settings tab
Select Manually Download and Upgrade from the drop menu list options.
Select the relevant Upgrade Version from the drop menu list.
Click the UPGRADE NOW button.

Screenshot

2 - Automatically Upgrading the DAC Version - To automatically upgrade your DAC to the latest version perform the following steps:

Select Upgrade Automatically from the drop menu list options.
Click the SAVE button to lock the upgrade mode in Satori.
Setting Maintenance Schedule - Set the download and upgrade timeframe (UTC) according to your system requirements to automatically upgrade to the latest recommended version.
Click SAVE.

Screenshot

3 - Deploy a Specific DAC Version - To deploy a specific DAC upgrade perform the following steps:

Select Deploy a Specific Version from the drop menu list options.
Click the SAVE button to lock the upgrade mode in Satori.
Select the relevant upgrade version according to your requirements.
Click UPGRADE NOW to upgrade the DAC

Screenshot

Satori Product Version Releases

New versions are made available on a weekly basis. Release notes are available here. Satori recommends that versions are regularly updated to enjoy new features, bug fixes and security patches. In the event of a critical fix, the Satori Customer Success team will contact customers directly via predefined communication channels to notify of the availability of the patch and discuss the recommended course of action.

Managing a Customer Hosted DAC

To ease managing customer-hosted Data-Access-Controller Satori provides a management app which enables the user to perform various debug & maintenance operations directly on the Data-Access-Controller.

Accessing the Satori DAC Management Interface

To access the Satori DAC Management interface perform the following tasks:

Click the Satori Settings Tab
Select the DAC view from the available options.
Now, click the hyperlink that appears after the name of your DAC instance in the table.

Screenshot

Upload logs - When performing a troubleshooting session with a Satori engineer you may be required to upload your DAC log files to a dedicated storage location. The log files are automatically deleted after 30 days.
Log Level Change - Satori engineer may also require that you change the log level for one of the modules, the log level will reset itself to the default state.
Configuration Reload - In the event that the Satori DAC detects an invalid configuration via the Satori Management Console, Satori will maintain the last valid configuration and not update to a newer version. The interface allows you to restore the DAC update mechanism, >

The Configuration Reload operation should only be performed once the Satori engineer has solved the problem that caused the DAC to stop accepting new configurations.

GitOps Based Deployment

Satori helps automate the process of deploying to a cluster via GitOps based infrastructure (e.g. Argo CD).

To enable the automation process, download the deployment package from the management console and then push the helm content into a chart repo.

Reference Script

A reference script and additional details are available on the dac_tools github repo.

Migrating a DAC to a New Kubernetes Cluster

Kubernetes supports performing a variety of maintenance operations in-place, without disrupting the workloads deployed on the cluster. Because the Satori DAC maintains some state on users and their sessions to data stores, the process of migrating the DAC from one cluster to another needs careful planning and consideration.

Before Migrating to a new Cluster

Perform the following steps before you start the migration process:

Create the new Kubernetes cluster for Satori.
Update any network policies configured on your data stores to include the IPs of the new cluster.
Communicate to your data consumers that a maintenance operation will take place at an agreed upon time.

Migration Process

Perform the following steps to migrate the Satori DAC to a new cluster:

Follow the first-time installation process to deploy the DAC on the new cluster.
Test the proxy-functionality (if relevant) on the new cluster by pointing a database client to the new DAC. Configure a hosts file entry on your workstation to point your network to the new cluster's load-balancer:
1. Get the new cluster's load-balancer IP address. For example, if the load-balancer of the new cluster is k8s-satoriru-satoriru-b8321e97a-3790e137d5d9ef3c.elb.us-east-1.amazonaws.com run the following:
  
  dig k8s-satoriru-satoriru-b8321e97a-3790e137d5d9ef3c.elb.us-east-1.amazonaws.com
2. Add the following entry to your hosts file. For example, if the DAC's domain name is dac1.us-east-1.a.p1.satoricyber.net add the following entry:
  
  <IP> dac1.us-east-1.a.p1.satoricyber.net
3. Try to connect to a data store protected by the DAC from a database client tool.
  
  NOTE: Temporary credentials may not work at this stage as they may be already cached in the old cluster. Test with local database credentials.
Change your DNS settings to point the DAC's domain to the new load-balancer hostname. For public-facing DACs using the satoricyber.net subdomain, please contact Satori Support to apply the change. Once the DNS change has been made, new connections will be routed to the new DAC, while existing connections will be routed to the old DAC.
To prevent any conflicts between the old and the new DAC, uninstall the old DAC after making the DNS change. To uninstall the DAC run the following:

helm uninstall runtime -n satori-runtime

After Migrating to a new Cluster

Perform the following steps after migrating the Satori DAC to the new cluster:

Temporary credentials need to be re-generated by users.
Update any network policies configured on your data stores to remove the IPs of the old cluster.
For Snowflake Proxy, it is recommended for users to logoff and log on again to Snowflake after the migration is complete. Consider using Snowflake's SYSTEM$ABORT_SESSION command to centrally abort sessions.