Reconfigure Front URL for manual Kubernetes Installation

Follow

Introduction

Changing the front URL of your platform after a manual Kubernetes installation is a common requirement, especially when moving from an IP address-based access to a more user-friendly domain name. This guide provides step-by-step instructions on how to reconfigure your front URL on a system with a manual Kubernetes installation.

Prerequisites

• A manual Kubernetes installation.
• Administrative access to your Linux environment.
• An SSL certificate (if HTTPS is used).

Step-by-Step Guide

Step 1: Prepare SSL Certificate

If you're using an SSL certificate for a secure (HTTPS) connection:

• Ensure that your SSL certificate and key files are located in the \dataclarity\template\certs\ directory on your server.
• Rename these files to cert.crt and cert.key.

Note: If your certificates are managed by an external load balancer, you can skip this step.

Step 2: Re-Execute the Install Script

• Locate the install.sh script in your installation directory.
• Run the script by executing the following command:

./install.sh

• When prompted for 'Enter the public entry point', input your new domain name.

Step 3: Verify the Changes

• After the script execution completes, verify the changes by accessing your platform using the new domain name. Ensure that all services are running correctly and that there is no data loss.

Step 4: Update DNS Records (if applicable)

• If you haven't already, update your DNS records to point to the server's IP address where your Kubernetes cluster is hosted.

Step 5: Test Your Setup

• Test the accessibility and functionality of your platform on the new domain.
• Confirm that all links and functionalities work as expected.

Troubleshooting

• If you encounter any issues during this process, check the log files for any error messages.
• Ensure that your domain name is correctly configured and propagated.
• Verify that your SSL certificates are correctly installed and configured if using HTTPS.

Data Preservation

• Provided that you maintain the same database configuration settings, rest assured that upon executing the install.sh script, all existing assets, including users, data connections, datasets, and storyboards, will be preserved and remain unaffected throughout this process.