-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated README and yml files #249
updated README and yml files #249
Conversation
@jpinsonneau The flp-daemonset-cap.yml doesn't yet work properly. Some permissions probably need to be adjusted. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #249 +/- ##
==========================================
+ Coverage 33.86% 34.06% +0.20%
==========================================
Files 39 39
Lines 3479 3508 +29
==========================================
+ Hits 1178 1195 +17
- Misses 2233 2243 +10
- Partials 68 70 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
2e42c0f
to
e9c4ad3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed perms in a023a01 and changed the instructions order to create namespace properly at first command.
@KalmanMeth note that if you are using oc
command, ommiting labels
section for pod-security
is actually working !
Using kubectl
, you must specify labels
🙃
deployments/README.md
Outdated
kubectl create namespace netobserv | ||
curl -S -L https://raw.githubusercontent.com/netobserv/documents/main/examples/zero-click-loki/1-storage.yaml | kubectl create -n netobserv -f - | ||
curl -S -L https://raw.githubusercontent.com/netobserv/documents/main/examples/zero-click-loki/2-loki.yaml | kubectl create -n netobserv -f - | ||
''' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to keep loki in the examples ?
We could simply have stdout here and then the users can dig into different export capabilities.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong preference. The existing example assumed loki, so I kept it that way. I simply added the instructions on how to bring up loki so that it will work.
I'm getting flows in FLP after applying the new changes:
|
To get rid of these messages, we need to change |
@jpinsonneau Can you merge your commit with this PR? |
It's already part of this PR, we can merge as is to me. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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:
Approvers can indicate their approval by writing |
Description
The stand-alone ebpf and flp were implemented against an older version of flp.
This PR updateds the README and yml files to work with the current flp.
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.