From 1c8f36db46f1f22d6e90bbcbfb0a367c4d151f5f Mon Sep 17 00:00:00 2001 From: Peter Valdez Date: Tue, 4 Jun 2024 02:46:50 -0400 Subject: [PATCH] Clarify the ingress logic in README --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 051b54f..4ffd7d6 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ Snorlax is a Kubernetes operator that wakes and sleeps a set of Kubernetes deployments on a schedule. -If you specify ingresses, a request to any of the ingresses will serve a cute sleeping Snorlax page served and the Kubernetes deployments are woken up. +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. You create `SleepSchedule` resources to define the schedule for deployments (and optionally their respective ingresses). @@ -117,7 +117,6 @@ make dev-run - Select deployments & ingresses by label - Support wildcards for deployment & ingress names - ## Reach out Wondering how to best use Snorlax? Have questions or ideas for new features?