From 7cb3db32ef29215d2dcd7454dea3571fa94739c2 Mon Sep 17 00:00:00 2001 From: Peter Valdez Date: Tue, 4 Jun 2024 02:47:51 -0400 Subject: [PATCH] Further clarify the ingress logic in README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4ffd7d6..ae90415 100644 --- a/README.md +++ b/README.md @@ -6,8 +6,8 @@ Snorlax is a Kubernetes operator that wakes and sleeps a set of Kubernetes deployments on a schedule. -If you specify ingresses, they are updated to serve a wake proxy which serves a cute sleeping Snorlax page and wakes the deployments up. -Once the deployments are ready, the page will auto-refresh. +If you specify ingresses, they are updated to serve a wake proxy which serves a "sleeping" splash page and wakes the deployments up. +Once the deployments are ready, the ingresses are restored and the splash page will auto-refresh. You create `SleepSchedule` resources to define the schedule for deployments (and optionally their respective ingresses).