Separate the crds from the operator manifests

Trying to install the operator with flux kustomization pointing to the manifest directory results in error relating to crds being duplicated. Signed-off-by: Omar Mohamed <[email protected]>
dragonflydb · Aug 26, 2024 · 5c4ab16 · 5c4ab16
1 parent a738101
commit 5c4ab16
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -25,7 +25,7 @@ Make sure to have your Kubernetes cluster up and running. Dragonfly Operator can
 
 ```sh
 # Install the CRD and Operator
-kubectl apply -f https://raw.githubusercontent.com/dragonflydb/dragonfly-operator/main/manifests/dragonfly-operator.yaml
+kubectl apply -f https://raw.githubusercontent.com/dragonflydb/dragonfly-operator/main/manifests/operator/dragonfly-operator.yaml
 ```
 
 By default, the operator will be installed in the `dragonfly-operator-system` namespace.
@@ -106,7 +106,7 @@ This will automatically delete all the resources (i.e pods and services) associa
 To uninstall the operator, you can run
 
 ```sh
-kubectl delete -f https://raw.githubusercontent.com/dragonflydb/dragonfly-operator/main/manifests/dragonfly-operator.yaml
+kubectl delete -f https://raw.githubusercontent.com/dragonflydb/dragonfly-operator/main/manifests/operator/dragonfly-operator.yaml
 ```
 
 ## License

diff --git a/manifests/crd.yaml → manifests/crds/crd.yaml b/manifests/crd.yaml → manifests/crds/crd.yaml
diff --git a/manifests/dragonfly-operator.yaml → manifests/operator/dragonfly-operator.yaml b/manifests/dragonfly-operator.yaml → manifests/operator/dragonfly-operator.yaml