Configuring grpc and configmap options through helm or directly should be
advanced configuration out of the box helm should just work.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

I don't think anyone will reasonably assume that the "Try Tetragon.."
section is a production users guide on how to deploy and manage a
fleet of servers running Tetragon.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Developers are not normal users lets build them their own docs sections
so as to not confuse development, from deployment, from exploration.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

To get started I don't think understanding all the details of JSON events
vs GRPC and so on is important. Move it into a "concepts" section.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Metrics are a great way to pull useful information out of Tetragon lets
create a section for them in Concepts.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Filtering by namespace and pod labels is part of tracing policy move it
under that unbrella item.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

There are lots of details we have for Installing Tetragon in various
environments, bare-metal, docker, systems, etc. Lets create a section
to capture those instead of spreading that knowledge thorughout and/or
in getting started which needs to be really about shortest path to
up and running tetragon.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

References should be after content IMO.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Tetra CLI is useful for sure lets move it into installation. The getting
started section can give the one line command to install it.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Enforcement is a big enough concept we can build its own section.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Lets document how we do benchmarks bring on the fun.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Simplify the getting started guide

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

This is nicer if a service is added later presumably it will
also pull from this cidr.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Large JSON event block is best to put in hidden block.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Per Mahe's comment its best to align headers and files.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Tetragonon should be tetragon

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Create an installation section and move systemd install there. This further
simplifies 'getting started' section.

Signed-off-by: John Fastabend <john.fastabend@gmail.com>

Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>

Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>

Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>

Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>

Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>