From 6c993b86055934d92596659a473ebfa7f1ea7fab Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 3 Dec 2025 09:23:08 +0000
Subject: [PATCH 1/2] Initial plan


From 39ee661e321a3a82c7522a0f45c6a57c00e95a3f Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 3 Dec 2025 09:25:33 +0000
Subject: [PATCH 2/2] Fix StatefulSet name references in k8s documentation

Co-authored-by: sfroment <7238385+sfroment@users.noreply.github.com>
---
 docs/k8s.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/k8s.md b/docs/k8s.md
index 90a2189..02cdbe1 100644
--- a/docs/k8s.md
+++ b/docs/k8s.md
@@ -158,7 +158,7 @@ If you hit `pod has unbound immediate PersistentVolumeClaims` errors, make sure
 Check that all resources are created:
 
 ```bash
-kubectl get sts mojave-sequencer-deployment -n 1sixtech
+kubectl get sts mojave-sequencer -n 1sixtech
 kubectl get pods -n 1sixtech
 kubectl get svc mojave-sequencer -n 1sixtech
 kubectl get pvc -n 1sixtech
@@ -168,8 +168,8 @@ kubectl get lease sequencer-leader -n 1sixtech -o yaml
 You should see:
 
 - 2 pods (or however many replicas you configured) with `app=mojave-sequencer`.
-- A StatefulSet `mojave-sequencer-deployment` reporting ready replicas.
-- Per-pod PVCs named like `sequencer-datadir-mojave-sequencer-deployment-0`.
+- A StatefulSet `mojave-sequencer` reporting ready replicas.
+- Per-pod PVCs named like `sequencer-datadir-mojave-sequencer-0`.
 - A single `Lease` named `sequencer-leader` with one of the pods listed as the current holder.
 
 #### 2.6 Check that the current leader is producing blocks (via logs)