From 9f95583f770c2b1f63f06cc75d39fc3c956d4710 Mon Sep 17 00:00:00 2001
From: dprotaso <dprotaso@gmail.com>
Date: Fri, 11 Feb 2022 09:40:04 -0500
Subject: [PATCH] Reduce the period and failure threshold for activator
 readiness

The default drain timeout is 45 seconds which was much shorter than
the time it takes the activator to be recognized as not ready (2 minutes)

This was resulting in 503s since the activator was receiving traffic when it
was not expecting it
---
 config/core/deployments/activator.yaml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/config/core/deployments/activator.yaml b/config/core/deployments/activator.yaml
index 2c18bac59f83..2376144320ec 100644
--- a/config/core/deployments/activator.yaml
+++ b/config/core/deployments/activator.yaml
@@ -104,13 +104,15 @@ spec:
             httpHeaders:
             - name: k-kubelet-probe
               value: "activator"
-          failureThreshold: 12
+          periodSeconds: 5
+          failureThreshold: 1
         livenessProbe:
           httpGet:
             port: 8012
             httpHeaders:
             - name: k-kubelet-probe
               value: "activator"
+          periodSeconds: 10
           failureThreshold: 12
           initialDelaySeconds: 15