-
Notifications
You must be signed in to change notification settings - Fork 918
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
feat(proposal): Adding artifacts scope and proposal #1184
Conversation
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.
Thanks for submitting this. I understand the goal of clarifying Falco artifacts and docker images.
Anyway, I did an initial review and left some comments. Please read them.
There are various points I think need attention.
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.
Although I like the spirit of this proposal, I think there're still some details that should be refined or simplified. In general, I believe we should slim down the set of officially supported artifacts.
Please see my suggestions.
Thank you!
I'm going to refine this proposal as discussed privately! |
c8a2f93
to
e817961
Compare
- Highlights scope of Falco - Highlights subprojects and groups evolution - Defines build artifacts - Defines artifact naming convention - Dictates that we take action to make these changes happen Signed-off-by: Kris Nova <[email protected]>
Signed-off-by: Kris Nova <[email protected]>
Signed-off-by: Kris Nova <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]> As per https://github.com/falcosecurity/falco/pull/1184/files#r420856406
Signed-off-by: Leonardo Grasso <[email protected]>
…t image naming Signed-off-by: Leonardo Grasso <[email protected]>
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.
It's OK for me.
I suggest to squash commits before removing "hold"
LGTM label has been added. Git tree hash: 75cf9aad7c97aec07f6cf9a278d629c80c4b1c53
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fntlnz, leodido, leogr 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 |
/honk |
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold cancel |
Signed-off-by: Kris Nova [email protected]
What type of PR is this?
/kind cleanup
/kind design
/kind documentation
Any specific area of the project related to this PR?
/area proposals
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: