diff --git a/test.md b/test.md
new file mode 100644
index 0000000..4c6acc3
--- /dev/null
+++ b/test.md
@@ -0,0 +1,66 @@
+# Kubernetes Resources Analysis and Troubleshooting Guide
+
+This guide aims to analyze Kubernetes resources based on available information, identify potential issues or areas for performance improvement, and provides detailed troubleshooting steps. 
+Before we begin, make sure that `kubectl` is configured to interact with your cluster. Use the command `kubectl config view` to confirm.
+
+## Analysis of Available Information
+
+The existing content provided is a `ClusterRoleBinding` resource named `calico-kube-controllers`. It binds the cluster role `calico-kube-controllers` to the service account `calico-kube-controllers` in `kube-system` namespace. 
+
+There also exists Prometheus metrics data that provides insights into the performance aspects of a Go application. This data includes garbage collection duration, allocated memory, and Goroutine count, among other things.
+
+## Identified Issues and Recommendations
+
+Given that no explicit errors or issues are given in the provided data, the guide will discuss some hypothetical issues that could occur based on the type of data provided:
+
+1. **RoleBinding Issues:** Potential issue can occur if the service account `calico-kube-controllers` doesn't exist, or it is in a different namespace other than `kube-system`. The `ClusterRole` `calico-kube-controllers` may also not exist.
+    - Recommendation: Confirm that the service account and ClusterRole exists. Use the following commands:
+      - `kubectl get serviceaccounts calico-kube-controllers -n kube-system`
+      - `kubectl get clusterroles calico-kube-controllers`
+
+2. **Go App Performance Issues:** If the metrics of `go_memstats_alloc_bytes_total` consistently show a high amount of bytes allocated or if the `go_goroutines` count keeps increasing without coming down, it might suggest a memory leak or high CPU usage issue.
+    - Recommendation: It is recommended to profile the Go application for potential memory leaks or CPU intensive routines.
+
+Let's proceed to the troubleshooting process.
+
+## Step-by-Step Troubleshooting Guide
+
+### Verifying RoleBinding Configuration
+
+1. Verify the service account:
+
+    ```sh
+    # This should return the service account details
+    kubectl get serviceaccounts calico-kube-controllers -n kube-system
+    ```
+
+2. Verify the `ClusterRole`:
+
+    ```sh
+    # This should return the cluster role details
+    kubectl get clusterroles calico-kube-controllers
+    ```
+
+### Profiling the Go Application
+
+Profiling Go applications require the use of pprof package. Follow the guide [here](https://golang.org/pkg/net/http/pprof/) to get started with profiling your Go application.
+
+## Mermaid Flowchart
+
+```mermaid
+graph TD
+  A{Start Profiling} --> B{Is memory consumption increasing over time?}
+  B -->|Yes| C[There might be a memory leak in your Go app]}
+  B -->|No| D{Are Go routines increasing over time?}
+  D -->|Yes| E[There might be Goroutine leakage in your Go app]
+  D -->|No| F[Go app working perfectly fine]
+  C --> G[End Profiling]
+  E --> G[End Profiling]
+  F --> G[End Profiling]
+```
+
+## Conclusion
+
+This guide provided an analysis of Kubernetes resources and insights on identifying potential bottlenecks. It is important to note that troubleshooting Kubernetes requires timely analysis of logs, events, and system metrics. Proactive monitoring and regular audits can help detect and prevent potential problems before they impact your system.
+
+*This document contains information generated by OpenAI's ChatGPT. This AI-generated content has not been independently verified and should be cross-checked against reliable sources.*