Managing licenses

Last published : Jul 06, 2026
A valid license is required before deploying InfoScale. The license is provided as a Kubernetes secret named infoscale-license in the infoscale-vtas namespace, containing Base64-encoded license data. This section covers creating, managing, and updating this secret. The secret must be present before upgrading to InfoScale 9.2.0.
Related information

Creating a license secret

  1. Create and configure the license secret using the following details.
    ---
    apiVersion: v1
    kind: Secret
    metadata:
        name: infoscale-license
        namespace: infoscale-vtas
    data:
        infoscale-license.lic: <base64 encoded lic data>
    type: Opaque
    Note: The license data must be Base64-encoded. You can encode your license file manually using the command: cat license.txt | base64 | tr -d '\n'. Alternatively, you can automatically handle the encoding and create the secret in one step by running: oc create secret generic infoscale-license -n infoscale-vtas --from-file=infoscale-license.lic=<license_file_location>.
    Or you can create the license through OLM.
    image
  2. Deploy license_cr.
    Verify the licensing details. Check the status of the license cr using the command: oc describe license.

Updating a license secret

Edit the secret YAML file to replace the data with a new, valid license.
Note: Ensure to renew your license well before expiry. The license data must be Base64-encoded. You can encode your license file manually using the command: cat license.txt | base64 | tr -d '\n'.Alternatively, you can automatically handle the encoding and update the secret in one step by running: kubectl create secret generic infoscale-license -n infoscale-vtas --from-file=infoscale-license.lic=<license_file_location> --dry-run=client -o yaml | kubectl apply -f -.
Or you can update the license through OLM.
image

License statuses

You can get the real-time status of InfoScale licenses by running oc describe license.
Monitor license resource status and LICO pod logs periodically to prevent any disruption.
Note: License renewals do not "carry forward" remaining time. When a new license file is applied, the expiration date is strictly set by the date defined in the new file provided by the support team.

License is valid

When your license is valid you'll get an output similar to the following.
Conditions:
    Last Transition Time:  2026-03-20T14:09:44Z
    Message:               License is valid until <date>.
    Reason:                LicenseValid
    Status:                True
    Type:                  LicenseValid

License is valid but is in the warning period

The license is within its warning period (typically 90 days prior to the expiration date). Contact support to renew.
Conditions:
    Last Transition Time:  2026-03-20T14:09:44Z
    Message:               License is expiring on <date>
    Reason:                LicenseInWarningPeriod
    Status:                True
    Type:                  LicenseValid

License is valid but is in grace period

The license has reached its expiration date, but the software remains fully functional for a set grace period.
Conditions:
    Last Transition Time:  2026-03-20T14:09:44Z
    Message:               License expired on <date> and it will be in grace period for <no.of remaining days> days
    Reason:                LicenseInGracePeriod
    Status:                True
    Type:                  LicenseValid

License is expired

The grace period has ended. InfoScale functionality will stop on these nodes until a new license is applied.
Conditions:
    Last Transition Time:  2026-03-20T14:09:44Z

    Message:               License expired on <date> and grace period ended on <date>.
    Reason:                LicenseExpired
    Status:                False
    Type:                  LicenseValid

License is invalid

Conditions:
    Last Transition Time:  2026-05-22T06:03:44Z
    Message:               License validation failed: vxlicrep ERROR V-21-1-63 Validation failed:License key is invalid or expired.
    Reason:                LicenseInvalid
    Status:                False

License recovery

When an InfoScale license expires and the grace period ends, the system enforces restrictions in stages. This results in complete application downtime — volumes, applications, and VMs become inaccessible until the license is renewed.
To recover an expired license
  1. Update the license secret
    kubectl create secret generic infoscale-license-n infoscale-vtas--from-file=infoscale-license.lic=<license_file_location>--dry-run=client-o yaml | kubectl apply-f-
    LICO detects the updated secret and immediately marks the license as valid.
  2. Restore storage services
    1. Reboot all nodes running InfoScale SDS pods simultaneously. This can be done by logging in to each host directly via SSH or through the server console.
    2. Post reboot wait till InfoScale cluster goes in running state and application should be up online. If there are issues seen please contact InfoScale support team.