Kubectl access to the stack. Refer to this document for preliminary instructions.
Admin console access of stack.
In the configuration section, scroll down to the end and check the "Launch reset Atlan instance job" option.
Scroll down to the bottom of the page and save the config. Your new product version has now been created.
To implement the changes, click on the "Go to the new version" button.
Now the system will perform the preflight checks. Click on "Deploy", once successful without any error.
Once the job is deployed from the admin console, we can fetch its logs and track its progress. Here is how you can do it:
Get Kubectl access to the instance.
Get the name of the reset job pod. Run this command, and copy the name of the pod starting with
reset-instance-job-. For example,
$ kubectl get pods -n kots
Tailing the logs of the reset-job pod.
$ kubectl logs reset-instance-job-fh24y5 -n kots -f
Wait for the job to finish.
Once you can job completion log from the pod, wait for sometime for all the pods to get up. Post that you can access the product and verify.
Check if all the pods are up using the command below:
$ kubectl get pods -A
Verify the product now.
Once everything is completed, follow these steps for cleanup.
Visit the release portal.
Go to the config section and uncheck the "Launch reset atlan instance job" option.
Save the config changes and deploy the newly created release.
If you face any issues in following these steps, you can always reach out to us at [email protected].