-
Bug
-
Resolution: Done
-
Major
-
netobserv-1.7
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
NetObserv - Sprint 261
-
None
-
None
-
Previously, when enabling the network policy via FlowCollector configuration, the traffic to the operator webhooks was blocked, breaking the FlowMetrics API validation. Now traffic to the webhooks is allowed.
When FlowCollector.networkPolicy is enabled, hence installing a network policy on netobserv namespace, is then becomes impossible to use the FlowMetrics API, as the netpol blocks calls to the validation webhook:
$ oc apply -f config/samples/flowmetrics/flows_with_flags_per_source.yaml Error from server (InternalError): error when creating "config/samples/flowmetrics/flows_with_flags_per_source.yaml": Internal error occurred: failed calling webhook "flowmetricvalidationwebhook.netobserv.io": failed to call webhook: Post "https://netobserv-webhook-service.netobserv.svc:443/validate-flows-netobserv-io-v1alpha1-flowmetric?timeout=10s": context deadline exceeded