KOTS - How to manually upload a new Jama license file

Jason De Paola
Jason De Paola

Author: Jason De Paola

Date: December 05, 2023

Audience: Everyone

Environmental details: Self-hosted

Summary: 

If required to manually upload a new Jama license file (.yaml) to KOTS Admin, these are the instructions. This works for both Internet and Airgap installations.

Solution:

1. Fetch the KOTS Admin config

kubectl kots get config jama-k8s -n default > config.yaml

 

2. Remove KOTS Admin

kubectl kots remove jama-k8s -n default -f

3. Restore KOTS admin with new license

  • Copy the license.yaml file to the app server or create a new file and paste the contents of the license.yaml file and save it somewhere on the app server filesystem.
  • Then, you can just run the following command where you need the config.yaml file from step 1 and the license.yaml file from the previous step:
kubectl kots install jama-k8s --app-version-label=9.0.3 --license-file license.yaml --namespace default --config-values config.yaml
 
*Note "--app-version-label=9.0.3" the version should be the current version you have deployed, e.g., 9.0.3
  • This shows a successful execution, after which the KOTS admin should be available with the new license and config restored.

Cause:

  • We have noticed that licenses sometimes fail to sync. Here is a method to push the license file and preserve KOTS Admin settings.

 

Please feel free to leave feedback in the comments below.

 

Related to

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

Comments

1 comment

  • Comment author
    Jenna

    Update: This procedure can also be used to swap license files in KOTS without disrupting the database and assets. 

    Use case: This was done successfully in a testing environment for a Jama Connect customer that wanted to keep their production environment up, create a new instance and migrate data over, then verify the data before decommissioning the previous app server and switch the license on the new instance from nonProd to prod.

    0

Please sign in to leave a comment.