Conduktor requires a license to enable features beyond the base features. The license can be put in the environment variables (this is recommended), or into the
As an environment variable
docker run command, you can add the -e flag to specify your license key, like this:
If you have many environment variables, you can write them in a file, and load this file using the --env-file flag.
For example, you can create a file named
env.list in which you write:
And then run the
docker run command with
Into the configuration file
On a far left justified line provide a
license configuration declaration. Example:
You have multiple ways to check that your license has been used to launch the Console.
In the logs
When you run the Console, you can find these meaningful logs in the head:
[ INFO platform_cli::license::validator] Input configured license : Some("YOUR_LICENSE_HERE")
[ INFO platform_cli::license::validator] License is valid ! Remaining days : 365
1.10.0 you can use the
/platform/api/license endpoint to get the license details.
curl -s http://localhost:8080/platform/api/license | jq .
Example of result:
Within the Conduktor Console container
You can get the same result as above from within the Conduktor Console container with the following command:
curl -s http://localhost:3000/platform/api/license
In the UI
In the Admin section, you can find the Clusters tab where there is the information of how many clusters you can create in your Organization.
You can also check through the different tabs that you have access to all the products you're supposed to have access to.
Renew or install a new license
To renew or install a new license, change the
license configuration in the
platform-config.yaml file, or the
CDK_LICENSE environment variable, depending on what you used. Then deploy the Conduktor Console container again.