Maintenance
This section describes the recommended steps to ensure regular maintenance of QALITA Platform to guarantee its performance, stability, and security.
Weekly Maintenance
1. Service Status Check
Ensure all services required by the platform are active:
Kubernetes:
kubectl get pods -n qalita
kubectl get pvc -n qalita
Docker Compose:
docker ps
docker volume ls
Check that all qalita-*
containers, as well as PostgreSQL, Redis, and SeaweedFS, are in a healthy
state.
2. Log Monitoring
Review recent logs to detect any potential errors:
kubectl logs <pod-name> -n qalita
Or in Docker:
docker logs qalita-backend
Inspect logs for the following services:
- Backend
- Agent
- SeaweedFS (filer and volume)
- PostgreSQL
Monthly Maintenance
1. Database Backup
Run a PostgreSQL backup:
pg_dump -U <user> -h <host> -p 5432 -F c -b -v -f qalita_backup_$(date +%F).dump qalita
Verify the integrity of the backup.
2. Cleanup of Obsolete Files
Manually clean up unused files on SeaweedFS (e.g., old pack results, very old logs).
3. Metrics Review
Check the volume of metrics:
- Database growth.
- Large SeaweedFS directories (
source
,output
,logs
, etc.). - Any metrics with repeated failures (from the graphical interface or via API).
Quarterly Maintenance
1. Platform Update
Helm / Kubernetes
helm repo update
helm upgrade qalita qalita/qalita -n qalita -f values.yaml
Docker Compose
Update images:
docker-compose pull
docker-compose up -d
Perform a full backup before each update.
2. User Access Review
Delete inactive users and modify roles if necessary. Go to the interface: Settings > Users & Roles
3. TLS Certificate Update
If you use manual certificates (without cert-manager
), remember to:
- Check expiration dates.
- Renew and redeploy certificates if necessary.
IV. License Verification
Check License Validity:
You can check the status of your license directly from:
- User Interface: Settings > License. If the license is nearing expiration, contact contact@qalita.io.
V. Maintenance Report Export
Compile the results of operations (pod status, errors, storage sizes, etc.) into a PDF or Markdown report for internal archiving or sharing with the QALITA team.
Conclusion
These maintenance operations are essential to ensure the longevity of your QALITA Platform instance. For any questions, contact our technical support.