Cloud-Native Upgrade Strategies

Docker Container Upgrades

Rolling Update with Docker Compose:

version: '3.8'
services:
  logserver:
    image: energylogserver/logserver:7.8.0
    deploy:
      update_config:
        parallelism: 1
        delay: 30s
        order: start-first
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
    volumes:
      - es-data:/usr/share/logserver/data
      - ./config/logserver.yml:/usr/share/logserver/config/logserver.yml

  logserver-gui:
    image: energylogserver/logserver-gui:7.8.0
    deploy:
      update_config:
        parallelism: 1
        delay: 30s

Kubernetes Upgrade Strategy:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: logserver
spec:
  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
  template:
    spec:
      containers:
      - name: logserver
        image: energylogserver/logserver:7.8.0
        readinessProbe:
          httpGet:
            path: /_cluster/health
            port: 9200
          initialDelaySeconds: 30
          periodSeconds: 10
        livenessProbe:
          httpGet:
            path: /_cluster/health
            port: 9200
          initialDelaySeconds: 60
          periodSeconds: 30

Helm Chart Upgrades

helm get values energylogserver > backup-values.yaml

helm upgrade energylogserver energylogserver/energylogserver \
  --version 7.8.0 \
  --values backup-values.yaml \
  --wait \
  --timeout 600s

kubectl get pods -l app=energylogserver
kubectl logs -l app=logserver

Terraform-Managed Upgrades

resource "kubernetes_stateful_set" "logserver" {
  metadata {
    name = "logserver"
  }
  
  spec {
    update_strategy {
      type = "RollingUpdate"
      rolling_update {
        max_unavailable = 1
      }
    }
    
    template {
      spec {
        container {
          name  = "logserver"
          image = "energylogserver/logserver:${var.els_version}"
          
          readiness_probe {
            http_get {
              path = "/_cluster/health"
              port = 9200
            }
            initial_delay_seconds = 30
            period_seconds       = 10
          }
        }
      }
    }
  }
}

Summary

This comprehensive upgrade guide provides detailed procedures for upgrading Energylogserver SIEM from any supported version. Key recommendations:

Best Practices:

  • Always create complete backups before upgrading

  • Test upgrades in staging environment first

  • Follow version-specific procedures carefully

  • Monitor system health throughout the process

  • Have rollback procedures ready

Critical Success Factors:

  • Adequate system resources (memory, storage, network)

  • Proper maintenance windows

  • Stakeholder communication

  • Post-upgrade verification

  • Performance optimization

Support Resources:

For complex environments or mission-critical deployments, consider engaging Energylogserver Professional Services for assisted upgrades and optimization.