Upgrading

Overview

This guide provides instructions for upgrading your Observo Manager installation. When performing an upgrade, it's important to follow these steps carefully to ensure data integrity and minimize downtime.

Pre-upgrade Steps

1. Check Current Version

helm list -n observo

2. Back Up Configuration

# Back up your current values
helm get values observo-manager -n observo > values-backup.yaml

# Back up database credentials
kubectl get secret postgres-auth -n observo -o yaml > postgres-auth-backup.yaml

3. Verify System Health

  • Ensure all pods are running:

    kubectl get pods -n observo

  • Check for any pending operations

  • Verify database connectivity

  • Review system logs for any issues

Upgrade Process

1. Update Container Images

# Extract new images
tar -xvzf new-airgapped_images.tar.gz
cd new-airgapped_images

Work with Observo team to upload new images to your registry.

2. Update Configuration

Update your values file with new version information:

global:
  version: "<new-version>"

3. Perform Upgrade

helm upgrade observo-manager ./observo-manager-<new-version>.tgz \
    --namespace observo \
    --values values.yaml

4. Monitor Upgrade Progress

# Watch pod status
kubectl get pods -n observo -w

# Check pod logs if needed
kubectl logs -n observo <pod-name>

Post-upgrade Verification

1. Verify Component Status

# Check all pods are running
kubectl get pods -n observo

# Verify services
kubectl get svc -n observo

2. Test Functionality

  1. Access the UI

    kubectl port-forward svc/observo-proxy -n observo 9000:9000

  2. Verify authentication is working

  3. Check data collection and monitoring

  4. Test critical features

Rollback Procedure

If issues occur during upgrade, follow these steps to rollback:

1. Initiate Rollback

helm rollback observo-manager -n observo

2. Verify Rollback

# Check helm release
helm list -n observo

# Verify pods
kubectl get pods -n observo

3. Restore Configuration

kubectl apply -f postgres-auth-backup.yaml

Common Issues

Image Pull Errors

  • Symptom: Pods stuck in ImagePullBackOff

  • Solution: Verify registry access and credentials

    kubectl describe pod <pod-name> -n observo

Component Upgrades

ClickHouse HA Migration

For migrating existing standalone ClickHouse to HA setup, see ClickHouse HA Migration Guide.

Next Steps

After successful upgrade:

  1. Remove old backups if no longer needed

For additional assistance, refer to:

PreviousHelm Chart Values ReferenceNextUninstall & Cleanup

Last updated

Was this helpful?