...
To check the current installed Kfuse version, run the following command:
| Code Block |
|---|
helm list |
Upgrading from Kfuse version 1.3.4 or earlier
Post-Upgrade
Pre-Upgrade
Kloudfuse alerts organization has changed with the introduction of additional alerts. New version does the organization automatically, however, the older alerts have to be removed. Please follow these instructions before continuing with upgrade. (These steps remove already installed Kloudfuse alerts).
Code Block # Connect to kfuse cluster and login to catalog service pod. kubectx <kfuse-cluster-name> kubens kfuse kubectl exec catalog-service-xxxxx-xxx -it -- bash # The following command will remove all alerts installed through the catalog service in folders hawkeye-alerts,kubernetes_alerts and kloudfuse_alerts python3 /catalog_service/catalog.py --artifact_type=alerts --remove_installed --list hawkeye-alerts,kubernetes_alerts,kloudfuse_alerts
Upgrading from Kfuse version 1.3.2 or earlier
Post-Upgrade
There is a schema change introduced in version 1.3.3. Make sure to restart the Pinot servers after upgrade completes.
...
Upgrading from Kfuse version 1.2.1 or earlier
Pre-Upgrade
Advance monitoring is available as an optional component in 1.3 and later releases. To enable:
Knight agent is required to be installed. Please review steps/settings here.
Additional agent settings required. Please review settings here.
Starting Kfuse version 1.3.0, Kfuse has added retention support using Pinot Minion framework. This feature requires changes to the existing Pinot Minion statefulset. The statefulset needs to be deleted prior to upgrade.
...
A breaking change related to the number of postgresql servers installed as part of the Kfuse install was introduced after Kfuse version 1.1.0. Due to this, the stored alerts will be deleted if directly upgrading Kfuse. In order to retain the stored alerts, run the following pre and post upgrade steps below. Note that until the post-upgrade steps are executed, alerts & dashboards from pre-upgrade will not show up.
Pre-Upgrade
| Code Block |
|---|
kubectl exec -n kfuse alerts-postgresql-0 -- bash -c 'PGPASSWORD=$POSTGRES_PASSWORD pg_dump -U postgres -F c alertsdb' > alertsdb.tar |
Post-Upgrade
| Code Block |
|---|
kubectl cp -n kfuse alertsdb.tar kfuse-configdb-0:/tmp/alertsdb.tar kubectl exec -n kfuse kfuse-configdb-0 -- bash -c 'PGPASSWORD=$POSTGRES_PASSWORD pg_restore -U postgres -Fc --clean --if-exists -d alertsdb < /tmp/alertsdb.tar' kubectl delete pvc -n kfuse data-alerts-postgresql-0 kubectl delete pvc -n kfuse data-beffe-postgresql-0 kubectl delete pvc -n kfuse data-fpdb-postgresql-0 |
...