Uninstall & Cleanup

Overview

This guide provides instructions for completely removing Observo Manager and its associated resources from your Kubernetes cluster. Follow these steps carefully to ensure proper cleanup and removal of all components.

Pre-cleanup Steps

1. Identify Resources

# List all resources in namespace
kubectl get all -n observo

# List persistent volumes
kubectl get pvc -n observo

2. Backup Important Data

Before proceeding, backup any important data:

# Backup configurations
helm get values observo-manager -n observo > values-backup.yaml

# Backup secrets
kubectl get secret postgres-auth -n observo -o yaml > postgres-auth-backup.yaml

Uninstallation Steps

1. Remove Helm Release

helm uninstall observo-manager -n observo

2. Delete Persistent Volume Claims

# List PVCs
kubectl get pvc -n observo

# Delete specific PVCs
kubectl delete pvc -n observo --all

3. Remove the Namespace

kubectl delete namespace observo

Additional Cleanup

1. Storage Cleanup

• Remove any external volumes

• Remove temporary files

2. Registry Cleanup

• Remove Observo Manager container images

3. Database Cleanup

If using external database:

• Archive or remove database used for observo

Verification

# Check for remaining resources
kubectl get all -n observo

# Verify PV cleanup
kubectl get pv | grep observo

Troubleshooting

Stuck Namespace

If namespace remains stuck in Terminating state:

1. Save namespace in JSON format:

   kubectl get namespace observo -o json > observo-ns.json

2. Edit observo-ns.json and remove finalizers

3. Update namespace:

   kubectl replace --raw "/api/v1/namespaces/observo/finalize" -f observo-ns.json

Stuck Resources

For resources stuck in deletion:

kubectl patch <resource-type> <resource-name> -n observo \
    -p '{"metadata":{"finalizers":[]}}' --type=merge

Best Practices

1. Order of Removal

   • Uninstall helm chart first

   • Delete PVCs next

   • Delete namespace only after other resources are gone

2. Data Protection

   • Backup all important data

Notes

1. Some resources might take time to delete due to finalizers

2. External resources might require manual cleanup

For additional assistance, refer to:

• Installation Guide

• Configuration Reference