-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
-
-
-
NetObserv - Sprint 237, NetObserv - Sprint 238, NetObserv - Sprint 239
Task to track Be able to install just the Kafka export feature in Network Observability testing status and addition of regression testing coverage.
- is related to
-
NETOBSERV-1058 QE: PerfScale Be able to install just the Kafka export feature in Network Observability
-
- Closed
-
[NETOBSERV-1057] QE: Be able to install just the Kafka export feature in Network Observability
thanks, in the 2 steps, I think we should make some extension to verification:
- Set consolePlugin.enable to false with loki.enable to true - ConsolePlugin pod is deleted and netflow-traffic tab is not seen on the console - and flows should be still ingested/fetched in/from loki ?
- Set consolePlugin.enable to true and loki.enable to false ConsolePlugin pod does not come up - I'd extend this to say, no errors are are seen in FLP logs as loki is disabled.
Updated the test-case to use DIRECT mode and included steps regarding consolePlugin enabling/disabling
Few comments:
> Deploy flowcollector with deploymentModel as KAFKA and exporter set
- is it necessary to have deploymentModel as KAFKA even though we use KAFKA only for export? In other words, couldn't we use deploymentModel as DIRECT and still export to KAFKA?
- you don't mention anything about consolePlugin.enable spec in your test case, we should probably add a step around that too unless there's a reason to leave it out? In what scenarios, we should set it to true/false and what should be the expected behavior?
Looks good.