Fix: Temporarily disable snap/k8sd config sync during snap upgrade (#…

…1164)

The snap and k8sd configurations are synchronized via k8s x-snapd-config in the configure hook. However, this process requires access to the k8sd API, which may be unavailable during an upgrade. For instance, in a clustered setup with microcluster, the upgrade process can be blocked until all nodes are on the same version, causing the reconciliation to time out.

We now explicitly disable the config sync during the snap upgrade to
avoid such scenarios.

snap/hooks/post-refresh

@@ -0,0 +1,10 @@
+#!/bin/bash -e
+. "$SNAP/k8s/lib.sh"
+
+k8s::common::setup_env
+
+# Enable the snap config reconciler after the snap refresh completes.
+# The reconcile command will synchronize the k8sd configuration with the snap config
+# and then set the meta orb to "snapd," effectively re-enabling the sync process.
+echo "Re-enabling snapd config sync after snap refresh"
+k8s::cmd::k8s x-snapd-config reconcile

snap/hooks/pre-refresh

@@ -0,0 +1,9 @@
+#!/bin/bash -e
+. "$SNAP/k8s/lib.sh"
+
+k8s::common::setup_env
+
+# disable snap set/get on snap refresh as microcluster need to sync first.
+# the sync will be enabled again after the refresh.
+echo "Disabling snapd config sync during snap refresh"
+k8s::cmd::k8s x-snapd-config disable