fix(kubectl-trace): restore status of the project

Signed-off-by: Lorenzo Fontana <[email protected]>

Author: fntlnz

README.md

@@ -73,6 +73,42 @@ Need more programs? Look [here](https://github.com/iovisor/bpftrace/tree/master/
 
 Some of them will not yet work because we don't attach with a TTY already, sorry for that but good news you can contribute it!
 
+## Status of the project
+
+:trophy: All the MVP goals are done!
+
+To consider this project (ready) the goals are:
+
+- [x] basic program run and attach
+- [x] list command to list running traces - command: `kubectl trace get`
+- [x] delete running traces
+- [x] run without attach
+- [x] attach command to attach only - command: `kubectl trace attach <program>`
+- [x] allow sending signals (probably requires a TTY), so that bpftrace commands can be notified to stop by the user before deletion and give back results
+
+
+**More things after the MVP:**
+
+<i>The stuff here had been implemented - YaY</i>
+
+<strike>The program is now limited to run programs only on your nodes but the idea is to have the ability to attach only to the user namespace of a pod, like:
+
+```
+kubectl trace run pod/<pod-name> -f read.bt
+```
+
+And even on a specific container
+
+```
+kubectl trace run pod/<pod-name> -c <container> f read.bt
+```
+
+So I would say, the next thing is to run bpftrace programs at a pod scope other than at node scope.</strike>
+
+**bpftrace work**
+
+I also plan to contribute some IO functions to bpftrace to send data to a backend database like InfluxDB instead of only stdout
+because that would enable having things like graphs showing 
 
 ## Contributing