Adding manifests of 2.13.0 (#3767)

* adding manifest of 2.13.0 Signed-off-by: Adarshkumar14 <adarsh.kumar@harness.io> * adding manifest of 2.13.0 Signed-off-by: Adarshkumar14 <adarsh.kumar@harness.io> Signed-off-by: Adarshkumar14 <adarsh.kumar@harness.io>
litmuschaos · Sep 15, 2022 · 41b546a · 41b546a
1 parent 0d06c4e
commit 41b546a
Show file tree

Hide file tree

Showing 9 changed files with 5,865 additions and 11 deletions.
diff --git a/litmus-portal/README.md b/litmus-portal/README.md
@@ -22,23 +22,23 @@ ChaosCenter provides console and UI experience for managing, monitoring, and eve
 
 #### Applying k8s manifest
 
-> Litmus-2.12.0 (Stable) Cluster Scope manifest
+> Litmus-2.13.0 (Stable) Cluster Scope manifest
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.12.0/mkdocs/docs/2.12.0/litmus-2.12.0.yaml
+kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.13.0/mkdocs/docs/2.13.0/litmus-2.13.0.yaml
 ```
 
 Or
 
-> Litmus-2.12.0 (Stable) Namespaced Scope manifest.
+> Litmus-2.13.0 (Stable) Namespaced Scope manifest.
 
 ```bash
 #Create a namespace eg: litmus
 kubectl create ns litmus
 #Install CRDs, if SELF_AGENT env is set to TRUE
-kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.12.0/litmus-portal-crds-2.12.0.yml
+kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.13.0/litmus-portal-crds-2.13.0.yml
 #Install ChaosCenter
-kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.12.0/litmus-namespaced-2.12.0.yaml -n litmus
+kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.13.0/litmus-namespaced-2.13.0.yaml -n litmus
 ```
 
 Or
@@ -99,7 +99,7 @@ View the User Guide <b>[here](https://docs.litmuschaos.io/)</b>
 ### **Local Development Guide for ChaosCenter**
 Local Development Guide for ChaosCenter can be found <b>[here](https://github.com/litmuschaos/litmus/wiki/ChaosCenter-Development-Guide)</b>
 
-### **Upgrade from 2.11.0 to 2.12.0**
+### **Upgrade from 2.12.0 to 2.13.0**
 
 You can upgrade using the steps from [section here](https://docs.litmuschaos.io/docs/user-guides/upgrade)
 

diff --git a/litmus-portal/manifests/cluster-k8s-manifest.yml b/litmus-portal/manifests/cluster-k8s-manifest.yml
@@ -635,9 +635,9 @@ spec:
             - name: EVENT_TRACKER_IMAGE
               value: "litmuschaos/litmusportal-event-tracker:ci"
             - name: ARGO_WORKFLOW_CONTROLLER_IMAGE
-              value: "argoproj/workflow-controller:v3.3.1"
+              value: "litmuschaos/workflow-controller:v3.3.1"
             - name: ARGO_WORKFLOW_EXECUTOR_IMAGE
-              value: "argoproj/argoexec:v3.3.1"
+              value: "litmuschaos/argoexec:v3.3.1"
             - name: LITMUS_CHAOS_OPERATOR_IMAGE
               value: "litmuschaos/chaos-operator:2.12.0"
             - name: LITMUS_CHAOS_RUNNER_IMAGE

diff --git a/litmus-portal/manifests/namespace-k8s-manifest.yml b/litmus-portal/manifests/namespace-k8s-manifest.yml
@@ -621,9 +621,9 @@ spec:
             - name: EVENT_TRACKER_IMAGE
               value: "litmuschaos/litmusportal-event-tracker:ci"
             - name: ARGO_WORKFLOW_CONTROLLER_IMAGE
-              value: "argoproj/workflow-controller:v3.3.1"
+              value: "litmuschaos/workflow-controller:v3.3.1"
             - name: ARGO_WORKFLOW_EXECUTOR_IMAGE
-              value: "argoproj/argoexec:v3.3.1"
+              value: "litmuschaos/argoexec:v3.3.1"
             - name: LITMUS_CHAOS_OPERATOR_IMAGE
               value: "litmuschaos/chaos-operator:2.12.0"
             - name: LITMUS_CHAOS_RUNNER_IMAGE

diff --git a/mkdocs/docs/2.12.0/litmus-portal-crds-2.12.0.yml b/mkdocs/docs/2.12.0/litmus-portal-crds-2.12.0.yml
@@ -1693,7 +1693,7 @@ spec:
                                                 allowed to see the host machine. Most
                                                 containers will NOT need this. More
                                                 info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath
-                                                --- TODO(jonesdl) We need to restrict
+                                                ## TODO(jonesdl) We need to restrict
                                                 who can use host directory mounts and
                                                 who can/can not mount host directories
                                                 as read/write.'