Added basic argo workflow docs and myhub troubleshooting methods (#151)

Signed-off-by: Amit Kumar Das <[email protected]>

Author: amityt

website/docs/assets/argo-chaos-workflow.png

@@ -59,3 +59,40 @@ If your problem persists, then delete all the cluster role bindings, PV and PVC
 You need to Provide the correct socket path. By default in Portal `CONTAINER_RUNTIME` is set to `docker`,
 If Your container runtime is `containerd` then you have to change the `CONTAINER_RUNTIME` to `containerd` and `SOCKET_PATH` to `/var/run/containerd/containerd.sock`.
 You can find these in tune experiments part of the tune workflow page.
+
+### We have installed ChaosCenter successfully but the Litmus ChaosHub is in error state and manual cloning of a Git repository does not work.
+It is most probably a network issue. Currently the ChaosHub feature is not supported in airgapped environment since it requires cloning of a remote git repository. Make sure you have an active internet connection to clone the git repository. If the issue still persists, you can manually add the git repository in the server pod. Here are the steps for the same:
+
+- Step 1: Exec inside the litmus-portal server pod and graphql-server container
+
+```
+kubectl exec -i -t <litmusportal-server> -n litmus --container graphql-server -- sh 
+```
+
+Check if the Chaos Charts directory is available. The directory structure is like 
+```
+/tmp/version/<project_id>/<hub_name>
+```
+
+Create these directories if not present inside /tmp/version/ :
+```
+mkdir <project_id> 
+cd <project_id> 
+mkdir <hub_name>
+```
+
+- Step 2: Clone the Chaos-Charts/Hub repository locally
+
+- Step 3: Use this command to copy the hub directory from your local system to the litmus-portal server pod
+
+```
+kubectl cp <location to chaos-chart/hub directory> <namespace>/<litmusportal-server-pod-name>:</tmp/version/<project_id>/<hub_name> -c graphql-server
+```
+
+
+Example: 
+```
+kubectl cp /home/amitkrdas/Chaos-Charts/chaos-charts/  litmus/litmusportal-server-6df9c5895d-57xx7:/tmp/version/686c1da2-da9c-4029-9c6a-528a9455a3b3/"Litmus ChaosHub" -c graphql-server 
+```
+
+- Step 4: Once the chaos charts directory is copied, refresh the ChaosHub page in ChaosCenter.

website/docs/troubleshooting.md

@@ -42,6 +42,13 @@ The graph consists of useful information such as :
 - Total time taken for the nodes to execute.
 - Structure of the experiments (Serial or Parallel experiments).
 
+You can also visualize the non Chaos workflows. The logs of individual nodes are also available here.
+
+<figure>
+<img src={require('../assets/argo-chaos-workflow.png').default} alt="Workflow run graph of a non chaos workflow" />
+<i>Graph of a non Chaos Workflow</i>
+</figure>
+
 ## View logs of individual nodes
 
 you can click on the nodes to get the logs of that particular step. If the revert-chaos step is disabled, the complete logs are available which include the runner pod logs and the chaos logs.

website/docs/user-guides/observe-workflow.md

@@ -50,7 +50,11 @@ In this step, you can create a workflow from different methods, these include:
 
 - **Create a new workflow using experiments from MyHub** : With this option, you can create customized workflows from the one of your connected ChaosHubs. With this option you can add multiple experiments from that ChaosHub either serially or in parallel to construct your workflow graphically.
 
-- **Import workflow using YAML** : With this option, you can import a [hand-crafted/constructed chaos workflow](construct-workflow.md) manifest and tune it according to the use-case.
+- **Import workflow using YAML** : With this option, you can import a [hand-crafted/constructed chaos workflow](construct-workflow.md) manifest and tune it according to the use-case. You can also import a basic Argo workflow using this functionality. 
+ :::note
+   For an uploaded workflow, the tune workflow functionality will not be available. The uploaded workflow is completely user-dependent or user-specific.
+
+
 
 ## 3. Workflow Settings