Skip to main content
Skip table of contents

Redis connectivity after successful service upgrade.

Problem

After upgrading the Redis services, the services are restarted and the pods addresses change. To reflect this change in pods that require Redis a manual pod restart is required. This is pertinent to any upgrades related to system-redis and redis in the upgrade panel.

🌱 Solution

Please perform the following steps exactly as described in the sequence as described below:

Requirements:

  • kubectl configured and available for cli interaction with your SIEMonster Kubernetes cluster.

Actions after upgrading System-redis in the [GLOBAL] section of the update panel:

  1. Run the following command, note that the <global_ns> should be replaced with the namespace that corresponds with your full domain e.g. in the case of domain example.siemonster.io the command would be kubectl -n example delete po $(kubectl -n example get pod | grep siemonster- | awk '{print $1}')

    BASH
    kubectl -n <global_ns> delete po $(kubectl -n <global_ns> get pod | grep siemonster- | awk '{print $1}')

Actions after upgrading Redis in the tenant section of the update panel:

  1. After you update, wait for 5 minutes then run the following command with <tenant_ns> replaced with the tenant name which you can see at the top right of the web interface e.g. kubectl -n tenant1 delete po $(kubectl -n tenant1 get pod | grep 'webreporting\|elastalert\|attack-map\|sclla-controller\|exporter' | awk '{print $1}')

BASH
kubectl -n <tenant_ns delete> po $(kubectl -n <tenant_ns> get pod | grep 'webreporting\|elastalert\|attack-map\|sclla-controller\|exporter' | awk '{print $1}')

NOTE: Step 2 will have to be repeated for each tenant after upgrading system-redis

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.