Verdict-as-a-Service

Get credentials

Credentials for testing Verdict-as-a-Service Cloud

If you’re interested in trying out Verdict-as-a-Service, you can easily create your own access data.

It should be noted that the access data provided are not intended for use in production systems or for the on-premises solution.

If you’re interested in our high-performance production systems or our on-premise solution, please don’t hesitate to get in touch using the contact information provided.

Get test Credentials for Verdict-as-a-Service On-premise

To access the VaaS docker containers, you have to provide at least one imagePullSecret.

To set the image pull secret, you need to create a custom values.yaml file that includes the necessary configurations for image pull secrets. Here’s how you can do it:

Direct Image Pull Secrets: If you have a direct image pull secret (a base64 encoded JSON containing Docker auth config), you can set it directly in the values.yaml file under either of these keys * global.secret.dockerconfigjson * global.secret.imagePullSecret * global.imagePullSecret

global:
  secret:
    dockerconfigjson: "BASE64_ENCODED_JSON_CONTAINING_DOCKER_AUTH_CONFIG"
    imagePullSecret: "BASE64_ENCODED_JSON_CONTAINING_DOCKER_AUTH_CONFIG"
imagePullSecret: "BASE64_ENCODED_JSON_CONTAINING_DOCKER_AUTH_CONFIG"

You can generate this value with a bash command like this

echo '{
        "auths": {
                "ghcr.io": {
                        "auth": "TO_BE_REPLACED"
                }
        }
}' | sed "s/TO_BE_REPLACED/$(echo "username:token" | base64 -w 0 )/g" | base64 -w 0

You need to substitute the username and password with the credentials we provided to you.

Global Image Pull Secrets: You can specify a list of predeployed image pull secrets under the global.imagePullSecrets key. These are the names of Kubernetes secrets that contain the registry credentials.

global:
  imagePullSecrets:
    - my-image-pull-secret