Documentation Hub
On-Premise
On-Premise
  • On-Premise Installation Manual
  • Keyless Backend Installation
    • Planning for installation
    • Components
  • Infrastructural requirements
  • Monitoring
  • Installation procedure
    • General Configuration
    • Namespace
    • Helm setup
    • Node Persistence
    • Circuit Storage
    • Core Daemon
    • Metrics Collector
    • Operations Service
    • Administrator Dashboard
  • Upgrade procedure
    • Cluster and Runtime
      • Breaking changes
        • Release 1.3.0
    • Databases
  • Checking the installation completed successfully
  • Helm and Components Versions
Powered by GitBook
On this page
  • Execution of the diagnostic
  • Configurable Options

Was this helpful?

Checking the installation completed successfully

Once the installation is complete the state of the system can be tested through the usage of the cct testing tool.

As for all other assets access to this tool is provided during the initial setup phase.

Execution of the diagnostic

This tool is dockerized and can be run from anywhere, provided a connection to the core-daemon is provided. The most convenient way to run it is by using a kubectl run command:

kubectl run -i cct --rm --image=quay.io/keyless_technologies/kl-cct-tester:master --env="APIKEY=some_valid_api_key" --env="HOST=http://core-daemon" --env="FULL_LOG=0" --image-pull-policy="IfNotPresent"

Example result:

If you don't see a command prompt, try pressing enter.
Starting tests..
> Performing ENROLL...
> ENROLL completed successfully!
> Performing AUTH...
> AUTH completed successfully!

All tests passed.
Goodbye.
pod "cct" deleted

This indicates that the system is running fine.

Configurable Options

APIKEY= must be set to a valid API Key recognized by the current installation
HOST= must point to the core-daemon host
FULL_LOG= 0 - minimal logging, 1 - verbose logging (useful for debugging purposes)

Last updated 2 months ago

Was this helpful?