Site Administration

This combined guide contains administration tasks for an Observo Site installation. It includes the full upgrade procedure followed by uninstallation and cleanup steps so operators can find administration-related workflows in one place.

Note: Throughout this guide, the namespace observo-client is used as the default. This namespace is replaceable—you can use any custom namespace for your Observo Site installation. Simply replace observo-client with your chosen namespace in all commands and configurations.

---

Upgrading

This guide provides instructions for upgrading your Observo Site installation to a newer version.

Prerequisites

Before starting the upgrade process, ensure you have:

• Current version details

• Access to the new version artifacts

• Backup of current configuration

Check Current Version

Get your current Observo Site version:

helm ls -n observo-client --filter '^observo-site$'

Preparation Steps

1. Backup Configuration

Get current Helm values:

helm get values -n observo-client observo-site > site-values-backup.yaml

2. Download New Configuration

1. Access Observo Settings page

2. Navigate to Site section

3. Download the latest Helm configuration

3. Update Configuration File

Important values to update:

• Image token

• Any custom configurations from previous deployment

Upgrade Procedure

1. Verify Prerequisites

# Check cluster status
kubectl get nodes
kubectl get pods -n observo-client

2. Deploy Upgrade

helm upgrade --install -n observo-client observo-site \
    oci://public.ecr.aws/e4z0a1h1/observo-site \
    --create-namespace \
    --set global.version="<new-version>" \
    --values=<helm-config-file>.yaml

Replace:

• <new-version> with the target version

• <helm-config-file> with your configuration file path

• observo-client with your custom namespace (if using a different namespace)

3. Monitor Upgrade Progress

# Watch pods
kubectl get pods -n observo-client -w

# Check rollout status
kubectl rollout status deployment/control-agent -n observo-client
kubectl rollout status deployment/data-plane -n observo-client

Post-Upgrade Verification

1. Check Component Status

# Verify all pods are running
kubectl get pods -n observo-client

# Check services
kubectl get svc -n observo-client

# Verify deployments
kubectl get deployments -n observo-client

2. Validate Functionality

• Verify Site status in Observo UI

• Check data ingestion

• Test existing pipelines

Rollback Procedure

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

1. Initiate Rollback

# Get previous release revision
helm history -n observo-client observo-site

# Rollback to previous version
helm rollback -n observo-client observo-site <revision-number>

2. Verify Rollback

# Check pod status
kubectl get pods -n observo-client

# Verify version
kubectl get deployment -n observo-client control-agent -ojson | \
    jq -r '.spec.template.spec.containers[0].env[] | select(.name == "SERVICE_VERSION") | .value'

For additional assistance or configuration details, refer to:

• Installation Guide

• Helm Values Reference

---

Uninstall & Cleanup

This guide provides instructions for completely removing Observo Site and its associated resources from your Kubernetes cluster.

Pre-cleanup Steps

1. Identify Resources

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

# List persistent volumes
kubectl get pvc -n observo-client

# List configmaps
kubectl get configmaps -n observo-client

# List secrets
kubectl get secrets -n observo-client

2. Backup Critical Data

# Backup Helm values
helm get values observo-site -n observo-client > site-values-backup.yaml

# Backup important configmaps
kubectl get configmap -n observo-client -o yaml > configmaps-backup.yaml

# Backup custom secrets if any
kubectl get secret <secret-name> -n observo-client -o yaml > secrets-backup.yaml

Uninstallation Steps

1. Remove Helm Release

# List helm releases
helm list -n observo-client

# Uninstall site
helm uninstall observo-site -n observo-client

2. Delete Persistent Volumes

# List PVCs
kubectl get pvc -n observo-client

# Delete specific PVCs
kubectl delete pvc -l app=observo-site -n observo-client

# Delete all PVCs in namespace
kubectl delete pvc --all -n observo-client

3. Remove the Namespace

kubectl delete namespace observo-client

Additional Cleanup

1. Load Balancer Cleanup

If using cloud providers:

# List services with load balancers
kubectl get svc -n observo-client -o wide

# Check cloud provider console for orphaned resources:
# - Load Balancers
# - Target Groups
# - Security Groups

2. DNS Cleanup

• Remove any DNS entries created for ingress

• Clean up external-dns resources if used

• Remove TLS certificates from cert-manager

3. Storage Cleanup

# List persistent volumes
kubectl get pv | grep observo-client

# Remove orphaned volumes
kubectl patch pv <pv-name> -p '{"metadata":{"finalizers":null}}'

Verification Steps

1. Verify Resource Removal

# Check for remaining resources
kubectl get all -n observo-client

# Check for persistent volumes
kubectl get pv | grep observo-client

# Verify namespace removal
kubectl get namespace observo-client

Troubleshooting

Stuck Namespace

If namespace remains in Terminating state:

# Get namespace details
kubectl get namespace observo-client -o json > ns.json

# Remove finalizers
# Edit ns.json to remove finalizers array

# Update namespace
kubectl replace --raw "/api/v1/namespaces/observo-client/finalize" -f ns.json

Stuck Resources

# For stuck PVCs
kubectl patch pvc <pvc-name> -n observo-client -p '{"metadata":{"finalizers":null}}'

# For other stuck resources
kubectl patch <resource-type> <resource-name> -n observo-client \
    -p '{"metadata":{"finalizers":[]}}' --type=merge