Docs: architecture + performance, scalability, resource consumption bounds + failure modes + coding guidelines

[fntlnz]

I was digging into the documentation at falco.org and couldn't find a document with the architectural details of falco.
It would be useful for new contributors and users since both need to understand what falco is doing in order to contribute and use it.

[leodido]

We also need this in order to match the CNCF due diligence technical requirements.
One example is the notary one.

[leodido]

I edited the title in order to use this issue as a reference also for other documents we need to write for the CNCF due diligence technical requirements.

Namely:

• document the performance, scalability, complexity, reliability, security trade-offs made, and whether they are tunable by the user or not
• document the failure modes
• document and enforce the coding guidelines
  • lua
  • c++
  • cmake
  • yaml
  • dockerfile
  • go

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fntlnz]

We still want this stalebot!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[leodido]

/help

[poiana]

@leodido:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.