mbp-1128: Add Network Observability with NooBaa-backed Loki - #165
Conversation
mlorenzofr
left a comment
There was a problem hiding this comment.
overall it's very good, but some small changes need to be made
abcf24c to
091415e
Compare
p-rog
left a comment
There was a problem hiding this comment.
Overall LGTM
I left one suggestion which I found when I was testing it at OCP 4.22.
Additionally, it would be great to add network policies to the Network Observability feature, to follow ZT methodology. You can test my network policy architect skill :)
I've added the the network policies |
89a748b to
04a245d
Compare
mlorenzofr
left a comment
There was a problem hiding this comment.
Overall okay, it's almost ready for LGTM in my opinion, just a couple of minor things.
Additionally:
- Change its status from draft to ready for review.
- Do a rebase to get the latest changes from the
mainbranch and avoid conflicts.
|
@pmatouse the network policies looks very nice. As I can see you didn't restrict specific ports in the ingress rules from Additionally, the Loki Operator channel is pinned to stable-6.6. To avoid OCP compatibility problems, maybe let's remove it like it was done with ODF, Quay, and RHTAS so subscriptions follow the default catalog channel on newer OCP releases. WDYT? |
Install Loki and Network Observability operators via a storage-dependent feature fragment, and deploy LokiStack plus FlowCollector using NooBaa storage. Signed-off-by: Petr Matousek <pmatouse@redhat.com>
Use Helm lookup for the default StorageClass when possible; require an explicit value under Argo CD. LokiStack CRD rejects an omitted field.
Enable FlowCollector operator NPs for netobserv/privileged, and add least-privilege policies for netobserv-loki.
04a245d to
b46e35c
Compare
|
Addressed in Also unpinned Loki channel in |
mlorenzofr
left a comment
There was a problem hiding this comment.
with the current code it is fully functional
If we want to avoid OutOfSync in the Argo CD application, we would have to ignore some attributes that mutate when the FlowCollector is initialized.
I may be wrong, but I think the SYNC-WAVE-INVENTORY.md file is missing the NetworkPolicies entries.
sabre1041
left a comment
There was a problem hiding this comment.
A few small changes. However, functionality wise, the new integration works great. Once these items are addressed, we can integrate
|
Done in c131741 — NetworkPolicies added to SYNC-WAVE-INVENTORY.md. |
feat: add Network Observability with NooBaa-backed Loki
Install Loki and Network Observability operators via a storage-dependent
feature fragment, and deploy LokiStack plus FlowCollector using NooBaa
storage.
Signed-off-by: Petr Matousek pmatouse@redhat.com