Add rollout restart and wait

Author: Prince Rachit Sinha

.werft/build.ts

@@ -398,7 +398,7 @@ export async function deployToDev(deploymentConfig: DeploymentConfig, workspaceF
 
     if (k3sWsCluster) {
         try {
-            registerK3sWsCluster(namespace, domain, "", getK3sWsKubeConfigPath())
+            await registerK3sWsCluster(namespace, domain, "", getK3sWsKubeConfigPath())
         } catch (err) {
             werft.fail(phases.REGISTER_K3S_WS_CLUSTER, err.toString())
         }
@@ -601,7 +601,14 @@ export async function triggerIntegrationTests(version: string, namespace: string
 }
 
 // Registers a WS cluster to the meta cluster
-function registerK3sWsCluster(namespace: string, domain: string, pathToKubeConfigMeta: string, pathToKubeConfigK3s: string) {
+async function registerK3sWsCluster(namespace: string, domain: string, pathToKubeConfigMeta: string, pathToKubeConfigK3s: string) {
+    // When we deploy the ws proxy then certs are not generate. So the pods could go into a long waiting state without kubelet reattempting to mount the volume
+    // So, we just restart the deployment for secrets to be mounted.
+    shell.exec(`export KUBECONFIG=${pathToKubeConfigK3s} && kubectl rollout restart deploy ws-proxy -n ${namespace}`)
+    shell.exec(`export KUBECONFIG=${pathToKubeConfigK3s} && kubectl rollout status deploy ws-proxy -n ${namespace}`)
+    // explicitly wait for 15s assuming the k3s service would have picked the new ws-proxy pod
+    await sleep(15000)
+
     gpctl.buildGpctlBinary()
 
     const wsProxyUrl = `ws-k3s.${domain}:8081`