Add direct-flp mode documentation

[jotak]

Description

Dependencies

n/a

Checklist

If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

• Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
• Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
• Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
• Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
• Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
• QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.08%. Comparing base (d4d25a4) to head (3797857).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #285   +/-   ##
=======================================
  Coverage   36.08%   36.08%           
=======================================
  Files          42       42           
  Lines        3786     3786           
=======================================
  Hits         1366     1366           
  Misses       2342     2342           
  Partials       78       78           

Flag	Coverage Δ
unittests	36.08% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[msherif1234]

in flp direct mode what will happen if ingest stage not omitted will the pod crash or just ignored ?

[jotak]

@msherif1234 it may either crash or perhaps result in some undefined behaviour. Currently there is nothing like a "pipeline config validation" in FLP, perhaps this is something we could work on. But the rule of thumb today is that the provided pipeline has to be consistent. Note that, the pipeline config isn't like some independent config flags where we could omit any of them: here all the stages are inter-connected and if there's something wrong it's likely that the whole pipeline config can be screwed up. It's not new with direct-flp.

[msherif1234]

/lgtm

[jotak]

thanks @msherif1234
/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