From f3dd36d049e309b2260a1d4de1a3cbb6824d71f4 Mon Sep 17 00:00:00 2001 From: Benjamin Durham Date: Mon, 3 Oct 2022 15:33:30 +1300 Subject: [PATCH] Fix rook-ceph namespace mismatch --- docs/kubernetes/persistence/rook-ceph/operator.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/kubernetes/persistence/rook-ceph/operator.md b/docs/kubernetes/persistence/rook-ceph/operator.md index 6210bf5..fa9a429 100644 --- a/docs/kubernetes/persistence/rook-ceph/operator.md +++ b/docs/kubernetes/persistence/rook-ceph/operator.md @@ -24,13 +24,13 @@ To start off with, we need to deploy the ceph operator into the cluster, after w ### Namespace -We need a namespace to deploy our HelmRelease and associated ConfigMaps into. Per the [flux design](/kubernetes/deployment/flux/), I create this example yaml in my flux repo at `/bootstrap/namespaces/namespace-rook-system.yaml`: +We need a namespace to deploy our HelmRelease and associated ConfigMaps into. Per the [flux design](/kubernetes/deployment/flux/), I create this example yaml in my flux repo at `/bootstrap/namespaces/namespace-rook-ceph.yaml`: ```yaml title="/bootstrap/namespaces/namespace-rook-ceph.yaml" apiVersion: v1 kind: Namespace metadata: - name: rook-system + name: rook-ceph ``` ### HelmRepository