Installing Valkey (Non-Production Ready)

This guide provides a minimal installation procedure for Valkey, a key dependency for your HCL UnO Agentic AI Builder application. This setup is not production-ready and has most features disabled by default. It is ideal for local testing or evaluation environments.

Note: If you followed the steps in the Installation and Configuration section, no changes are needed in the values.yaml file, these components are already configured correctly.

Valkey (Minimal Setup)

To deploy Valkey with basic authentication, you will need to create a Kubernetes Secret containing a generated password. Follow the steps below:

  1. Generate a Secure Password: Run the following command in your terminal to generate a 32-character alphanumeric password and encode it in base64:
    head /dev/urandom | tr -dc A-Za-z0-9 | head -c32 | base64
  2. Create the Kubernetes Secret: Replace <base64-password> in the YAML below with the output from the previous command. Save this content as valkey-secret.yaml:
    apiVersion: v1
    kind: Secret
    metadata:
      name: valkey-password-secret
    type: Opaque
    data:
      password: <base64-password>
    Apply this secret to your Kubernetes namespace using the following command:
    kubectl --namespace $NAMESPACE apply -f valkey-secret.yaml

    Replace $NAMESPACE with your target Kubernetes namespace.

  3. Install Valkey Using Helm: Use the official Bitnami Helm chart to install Valkey, referencing the secret you just created for authentication:
    helm --namespace $NAMESPACE install valkey \
      oci://registry-1.docker.io/bitnamicharts/valkey \
      --set auth.existingSecret="valkey-password-secret" \
      --set auth.existingSecretPasswordKey="password"

    Replace $NAMESPACE with your target Kubernetes namespace.

    Result: After completing these steps, Valkey will be installed with a minimal configuration in your specified namespace. This setup is primarily suitable for development and testing purposes and is not intended for production use. For production deployments, it is strongly recommended to consider enabling persistence, monitoring, TLS (Transport Layer Security), and other critical security and operational features.