hack: development using "make run" (with loki)

[eranra]

1. Updating the Makefile to allow deploy and undeploy of sample cr (there was some unneeded | etch command)
2. Adding Development documentation inside hack folder
3. Adding simple Loki deployment
4. Adding simple Loki Grafana deployment script

[jotak]

Currently we have some hacks in https://github.com/netobserv/documents , especially for loki & grafana, so I don't think we want to have that in two different places, however maybe it makes more sense to have it in the operator repo indeed.

Beside that, we haven't introduced much shell scripts yet, maybe we can keep using the makefile to add loki/grafana deploying targets? We could copy here the zero-click loki/grafana templates (https://github.com/netobserv/documents/tree/main/examples/zero-click-loki) and simply execute kubectl on that from a `deploy-loki| target, so that we keep the deployment logic all via make targets?

[eranra]

@jotak when I asked in slack and you and @stleerh provided two solutions I said to myself that we need something agreed and common for testing and experience with the operator. In flowlogs2metrics we have something that looks like https://github.com/netobserv/flowlogs2metrics/blob/main/Makefile#L128 ... it also deploys Grafana and Prometheus. Once we get the work from @OlivierCazade to deploy the dependent operator, maybe the script to deploy Loki will not be needed.

As for the hacking doc ... it was very helpful to me when I did the end-to-end tests with the console and flowlogs2metrics deployed with the operator ... especially https://github.com/netobserv/network-observability-operator/pull/61/files#diff-88be51eadd2c2ccdf0a6f5bb8255bbe4f37f2b887a6839f638bc45f6cfe18bb4R12-R26 are missing and should be added somewhere.

Please advise what you prefer to have here ...
(1) Close this PR and just save things locally
(2) Keep part of the PR for Hacking and remove other parts
(3) Keep all ...

From my PoV ./... working with make run i.e. https://github.com/netobserv/network-observability-operator/pull/61/files#diff-88be51eadd2c2ccdf0a6f5bb8255bbe4f37f2b887a6839f638bc45f6cfe18bb4R20 is very important and efficient and I really think that this might help others when they start to work with the oprerator.

[jotak]

I like the approach you have in FL2M, it's similar to our "zero-click-loki" wired in the Makefile, I think we could have the same here. And same for grafana.

Also +1 for documenting the make run approach, but it could actually be in the main readme and not in a separate hack doc.

[jpinsonneau]

+1 for make run

Also consider this new option for quick deploy #59
At the end, there is no need to manipulate anything else than the FlowCollector yaml

[jotak]

/lgtm

@memodi @jechen0648 there's a couple of changes in the Makefile here, not sure if it impacts some test cases / doc that you wrote. Not a big change, especially if you were using make create-sample you should change to make deploy-sample-cr once this PR is merged

[stleerh]

/lgtm

[jotak]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jotak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jotak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment