Page Comparison

...

• 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 of kfuse-ssd-gcp or kfuse-ssd-aws.

  Code Block
  kubectl get pvc -n kfuse

• Old alerts have to be removed. 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.

  • If currently using kfuse version older than 1.3.4:

    • Manually remove all alerts by navigating to the grafana tab and remove all alerts from kloudfuse_alerts and kubernetes_alerts folder.

  • If currently using kfuse version 1.3.4 or newer:

    • 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

...