...
Note: Kfuse services will go offline during this process. Kloudfuse storage class configuration has been simplified to keep future releases/features in mind. This requires running the migrate_storage_class.sh script provided by Kloudfuse team.
Code Block ./migrate_storage_class.sh
After running the script, ensure that the pvc’s storage class has
kfuse-ssd, instead ofkfuse-ssd-gcporkfuse-ssd-aws.Code Block kubectl get pvc -n kfuseKloudfuse 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
| View file | ||
|---|---|---|
|
Post-Upgrade
There is a schema change introduced in the traces table. Make sure to restart the Pinot servers after upgrade completes.
| Code Block |
|---|
kubectl rollout restart sts -n kfuse pinot-server-realtime
kubectl rollout restart sts -n kfuse pinot-server-offline |
Upgrading from Kfuse version 1.3.2 or earlier
...
Starting Kfuse version 1.2.0, cloud-specific yamls (aws.yaml, gcp.yaml, azure.yaml) are not included in the chart anymore. The custom_values.yaml needs to include these configurations. Refer to Configure Cloud-Specific Helm Values and Configure Cloud-Specific Storage Classes https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/793378845. With Kfuse version 1.2.0, there is no need to pull the chart prior to installation. helm upgrade can be directly run with the Kfuse helm chart registry.
...