Home
AppViewX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
OpenShift Deployment with ArgoCD
Creating Image Pull Secret

CERT+
Automate certificate lifecycle management including issuance, discovery, renewal, and deployment, across public and private trust CAs. Assess, prioritize, and plan your migration to quantum-safe encryption with the Quantum Trust Hub add-on module.
PKI+
Provision, govern and scale private trust certificates with a Post Quantum ready cloud based Enterprise PKI-as-a-Service.
SIGN+
Secure software, firmware, and containers with a comprehensive enterprise code signing solution.
SSH+
Control SSH access and key rotation at scale with an SSH key lifecycle management solution.
KUBE+
Unify DevOps and Security teams by managing certificates with a Kubernetes-native certificate lifecycle management solution.
DDI+
Manage domain registration, renewal, decommissioning, and other security controls with an end-to-end domain lifecycle management solution.
ADC+
Automate and orchestrate application delivery infrastructure at scale with an ADC lifecycle automation platform.
Platform
Manage policy and automation across all of the products and modules in the AVX ONE platform.
AppViewX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
Release Artifacts
Review new features, fixes, and security advisories with official AppViewX release documentation.

Creating Image Pull Secret

This is a mandatory step to be performed before installing the avx-infra.

Create a pull secret in the avx, avx-kafka, and kube-system namespace that would permit the pods to pull images from the intended image registry.
The default name of the secret is avx-image-pull-secret. If a different name is used then the image pull secrets’ name should match the name given in the values.yaml in both avx-infra and avx-app (imagePullSecrets) during installation
For HA (High Avaliability), 3 zones/datacenters are required. The pods will be distributed across those zones. Ensure that the nodes in the zones have the following label to identify which zone a particular node belongs to:
```
topology.kubernetes.io/zone
```
Example:
```
topology.kubernetes.io/zone=datcenter1
```