Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: netobserv-1.6.1
Affects Version/s: netobserv-1.6
Component/s: Operator
Labels:
- pre-merge-tested

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
Previously, when configuring custom subnet labels and keeping the OpenShift subnets auto-detection enabled, OpenShift subnets would take precedence over the custom ones, preventing the definition of custom labels for in cluster subnets.
With this patch, custom defined subnets take precedence, allowing the definition of custom labels for in cluster subnets.

Show
Previously, when configuring custom subnet labels and keeping the OpenShift subnets auto-detection enabled, OpenShift subnets would take precedence over the custom ones, preventing the definition of custom labels for in cluster subnets. With this patch, custom defined subnets take precedence, allowing the definition of custom labels for in cluster subnets.
Intelligence Requested:
Market:

Sprint:
NetObserv - Sprint 255, NetObserv - Sprint 256

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Here are the issues I encountered with subnet labels. Feel free to open separate issues for these two items.

1. OpenShift auto-detect is enabled by default despite the field being not enabled in Form view and despite what the doc says at https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md#flowcollectorspecprocessorsubnetlabels-1

In Web Console, I am unable to set it to false in Form view.

2. If OpenShift auto-detect is enabled, custom labels do not work. Is that intentional? Since `openShiftAutoDetect` is true by default, it doesn't show up in the YAML, Therefore, it seems like custom labels doesn't work at all until I figured out I have to explicitly set `openShiftAutoDetect` to false.