From 0f29b00b9f5427f8e6a5d11e401f5ec0168df2b3 Mon Sep 17 00:00:00 2001
From: Adrian Ludwin <aludwin@google.com>
Date: Tue, 29 Mar 2022 12:00:06 -0400
Subject: [PATCH] Add readiness probe

On GKE 1.21 and earlier, I noticed HNC taking a long time (~80s) to
become Ready (for more details, see #170). Adding a readiness probe
fixes the problem.

Tested: before this change, on GKE 1.20 and 1.21, I manually see HNC
taking a long time to start, and the e2e tests that require reinstalling
HNC fail because it the deadlines are exceeded. With this change, I can
see HNC becoming ready in ~10s on GKE 1.20 and all the e2e tests pass.
---
 config/manager/manager.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/config/manager/manager.yaml b/config/manager/manager.yaml
index 39b00134b..87b3e7d11 100644
--- a/config/manager/manager.yaml
+++ b/config/manager/manager.yaml
@@ -67,6 +67,11 @@ spec:
             port: 8081
           failureThreshold: 1
           periodSeconds: 10
+        readinessProbe:
+          httpGet:
+            path: /readyz
+            port: 8081
+          periodSeconds: 5
         startupProbe:
           httpGet:
             path: /readyz