Skip to main content

Downloading Aonnis Valkey Panther and Valkey Node Images

To deploy Aonnis Valkey Panther and Valkey clusters, customers need access to container images for both the Panther operator and Valkey nodes. This document explains how Aonnis handles image distribution and how customers can set up their Kubernetes environment to pull these images securely.

Image Distribution via Private Registry​

Aonnis automates the process of creating and managing a private container image registry for customers. Here’s how it works:

  1. Registry Creation:
    Aonnis Valkey Panther will create a private image registry for each customer. This registry will host:

    • Aonnis Valkey Panther images.
    • Valkey Conductor (Serves as an intermediary to manage and orchestrate operations on the pod) images.
    • Valkey Node images.

  2. Image Push:
    The required images will be pushed to the private registry by Aonnis.

  3. Credentials Availability:
    The credentials (username and password) for the private registry will be available on the Aonnis Web Console. Customers can retrieve these credentials from their account dashboard.

    1. The registry credentials provided for accessing Aonnis Valkey Panther and Valkey node images are designed to expire and refresh automatically. This ensures enhanced security while maintaining uninterrupted operations.
    2. Automatic Expiration: Credentials are periodically rotated to minimize security risks.
    3. Seamless Refresh: Aonnis Valkey Panther is designed to handle credential updates automatically, ensuring that the operator and Valkey clusters continue to function smoothly without manual intervention.
    4. Zero Downtime: The automatic credential refresh process ensures that there is no disruption in pulling container images or maintaining cluster operations.

  4. One private registry will be created for one Aonnis account.

tip

Registry credentials will only be available after creting your first license.

Setting Up Kubernetes to Pull Images​

To use the images in your Kubernetes environment, follow these steps:

Step 1: Retrieve Registry Credentials​

  1. Log in to the Aonnis Web Console.
  2. Navigate to the Registry Credentials section in the dashboard using sidebar.
  3. Copy the credentials for your private image registry.

Step 2: Create a Kubernetes Secret​

Use the retrieved credentials to create a Kubernetes secret for image pulling.

kubectl command to create image pull secret
kubectl create secret docker-registry avp-image-pull-secret \
   --docker-server=<registry-url> \
   --docker-username=<username> \
   --docker-password=<password> \
   --docker-email=<email>

Step 3. Annotate your secrete (Must be done)​

Image pull secret must be annotated as mentioned below. If not done properly then Aonnis Valkey Panther will not be able to recongnize image pull credentials.

kubectl command to aonnotate image pull secret
kubectl annotate secret avp-image-pull-secret \
  "app.kubernetes.io/managed-by=aonnis-valkey-panther" \
  "expiryDateTime=2025-02-01T10:32:58Z" \
  -n default
warning
  1. The expiry date should initially be set in the past. Aonnis Valkey Panther will automatically update it based on the Valkey Cluster license.
  2. Registry credentials have a set expiration period. If no Valkey Cluster is operational when the credentials expire, Aonnis Valkey Panther will be unable to refresh them. To ensure uninterrupted updates, at least one Valkey Cluster must remain active at all times. Otherwise, manual intervention will be required to update the registry credentials.