Testkube

note/atomsoftware
2 min read (205 words)

Architecture

You can deploy Testkube in one of the following ways:

  • Cloud:
    • Control Plane runs in the cloud
  • On-Prem:
    • Control Plane is managed by you (On premises)
  • Open Source:
    • (Standalone) Agent runs without a Control Plane

Features

Test Workflows

Examples

Gotchas

If you use a private registry for your images, check out Fetching Image Metadata from the Container Registry and Avoid Fetching Image Metadata

Companies may have a strict policy of not storing the credentials for the Container Registry in the Kubernetes’ Secret, or disallow Secrets at all. When Testkube does not have access to the Container Registry, it may revoke running the Test Workflow with errors about not being able to access the private image metadata.

To overcome this issue, you need to make sure that every step has the above data (workingDir, securityContext.runAsUser/runAsGroup) provided, and you cannot use the run operation without specifying the command. As an example, you may set the default container configuration as follows:

spec:
  container:
    workingDir: /data
    securityContext:
      runAsUser: 1000
      runAsGroup: 1000

Some images may be prepared to work correctly only with selected user/group IDs. In that case, the container may fail using the common one, and you will need to specify the expected one for this step.