Git Product home page Git Product logo

community's Introduction

Cloud Native Runtime Security.


Falco Community

The Falco community owns and maintains all aspects of The Falco Project. Every repository in the falcosecurity GitHub org belongs to the community.

Table of Contents

Resources

Community Calls

These are the primary calls for The Falco Project. If you are unsure where to get started, this is the place to join.

When: Weekly Community Calls on Wednesday at UTC 4pm.

You can see the Falco Calendar here .

If you want to subscribe to the Falco calendar, you can use this ics feed.

https://lists.cncf.io/g/cncf-falco-dev/ics/7639482/1350118793/feed.ics

Where: Zoom call

Falco Community calls gives the Falco community a common time to come together to discuss any open issues or PRs, new features, rules, upcoming releases, etc. Anyone can join, anyone can ask questions in the designed time but only the MC and the designed speakers (those that had allocated 10 mins slot during the week) will present. After every call, a report will be published in this repository with a summary of the call.

Minutes: We use the same hackmd document every week to track our minutes.

History: Check out the YouTube channel

All of our calls are documented and posted to the YouTube channel.

Running a call

Regardless if you are interested in starting a new call, or running an existing call we have some structure in place to drive these calls.

  • All new calls should include a calendar invite sent to the mailing list's email address [email protected], as well as a short description of the call and the goals.
  • All calls should be recorded and published to the Falco YouTube Channel
    • Note: Please contact a maintainer for access to the channel if you need to upload a video.
  • All calls should have written minutes using hackmd.io. Ideally the minutes are posted in advance to give collaborators a chance to add items before the meeting. After the meeting the notes should be closed, and uploaded to this repository.
    • Note: The template used for the Falco Community Calls can be found here
  • All calls must adhere to the CNCF Code of Conduct

Slack Channel

Join the #falco channel on Kubernetes Slack. We will be thrilled to meet you!

Mailing List

Join the Falco mailing list to keep you posted on important news and announcements.

How to contribute

See the contributing guide and the code of conduct.

Project Evolution

The falcosecurity/evolution repository is the official space for the community to work together, discuss ideas, and document processes. It is also a place to make decisions. Check it out to find more helpful resources.

community's People

Contributors

alacuku avatar anadee11 avatar andreagit97 avatar araujof avatar cpanato avatar danpop-chainguard avatar fededp avatar fntlnz avatar hackmd-deploy avatar jasondellaluce avatar jsalinas29 avatar krisnova avatar leodido avatar leogr avatar lucaguerra avatar markjacksonfishing avatar maxgio92 avatar mfdii avatar nibalizer avatar zuc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

community's Issues

Ownership of zoom room (community call)

What issue would you like to discuss?

Ownership of the community call's zoom room.

Details about the discussion

We need a way to handle its ownership in order to have the recording available to the whole team.

So that the team can then publish the recording on YouTube.

I want to know how to customize the rules after falco is deployed and how to trace back to fluentd to collect falco effective events

At present, I have deployed a set of falco examples through helm, but it seems that there are no rules by default. I found that only files can be created to be seen by falco, and no information can be seen in other created directories and deleted file directories, so I want to Please tell me, I’m sorry I don’t know if I am consulting here. I also want to know how the rules are defined, which can be added to the events in my production, how to collect the events in fluentd, and which should be reported to the police

GitHub and contribution automation

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue
/kind pr

/kind issue

Details about the discussion

I would like to discuss how automation could improve the contributing workflow to the Falco open source organization and to its repositories.

About this matter I already proposed a solution into the issue 621, where you can read more details about it.

In short, it presents prow, a tool which provides CI features as well as a set of plugins/bots/tools aimed at improving developers productivity and open source management by automating workflows as much as possible.

By the way, for completeness, you could see an initial automation in this repo itself (implemented by the test-infra one).

#falco-triage Slack Channel and curators maintainer group

What type of proposal is this?

/kind issue

Details about the discussion

I'd like to have a dedicated Slack channel where we can work solely on PR and issues triaging.

Q: What do you want want to achieve with this?
A: Our triaging process is automated via @poiana, that means that anyone in the community can start helping right now and do triaging via the slash / commands. However, not everyone has the same level of experience on the project. The purpose of this channel would be to create a group of people that discuss about triaging in Falco projects where they can cooperate on solving issues and merging PRs.

However, if you read the title there's also the "curators maintainer group". That means that I expect the most active users interacting with the falco-triage slack channel to be promoted as Falco Maintainers with a "curator" role.

By "curator" I mean: a Falco Maintainer who is in charge of taking care of the project issues and knows the Falco community well enough to them to the right people. Of course they can go and solve themselves the ones that they can take care of.

Of course since the curator is a different role with different requirements we will also need to update the governance file accordingly: https://github.com/falcosecurity/falco/blob/dev/GOVERNANCE.md#maintainer-responsibilities

Run slim or minimal falco docker container in an OS which Falco community does not provide a pre-built kernel probe module for

What type of proposal is this?

/kind issue

Details about the discussion

I want to run slim or minimal Falco docker container in an OS which Falco community does not provide a pre-built kernel probe module for. What would be the recommended option to install the Falco kernel probe?

Thanks to Michael, I already have 2 options

  1. Build Falco kernel probe module from source
  2. "Run falco as a container (the full image) on a 18.04.3 host like so. The only difference is to make /lib/modules rw (readwrite) instead of ro (readonly). The falco container will then move the module into the host's /lib/modules and you can copy it to a object store from there."

I am looking to see there is a third option where I do not have to run the full Falco container to install kernel probe, terminate the full container, and then run the slim Falco container.

More info in: falcosecurity/falco#890

Cutover to CNCF Slack

What issue would you like to discuss?

falcosecurity/falco#983

Can we please cutover from the Sysdig slack to the CNCF slack?

In order to make this as seamless as possible we can use the slack feature: https://slack.com/resources/slack-for-admins/shared-channels-in-slack

Please link the issue you would like to propose for discussion

Issue #number

Details about the discussion

We need to understand which sub-channels (if any) we have.

Where do we discuss tools like falcoctl or the prometheus-exporter?

Discuss coding conventions, formatters, and their integration in Falco workflow

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue

/kind pr

Details about the discussion:

  • Which coding style to adopt for Falco userspace C++ code?
  • Which format for Cmake files?
  • Which other formatters do we need (eg., python code for integration tests)?
  • How to integrate clang-format and cmake-format into the GitHub workflow?
  • Do we want to provide tools (eg., git presubmit hooks) locally or do we want an automatic job that performs the formatting if missing during PRs?

More here.

Testing prow

What type of proposal is this?

/kind pr

Details about the discussion

We are simply testing prow.

Improved Falco Ouputs

Hi,

I propose to talk about future of falco's outputs. Until now, outputs are quite simple and formatting is limited. We've already an issue of falco's repo side about with more details :

falcosecurity/falco#528

/kind issue

Falco test cases are failing on ppc64le platform

What type of proposal is this?
/kind issue

What issue would you like to discuss?
Build the Falco code on Ubuntu 18.04( kernel 4.15.0-66-generic) with eBPF flag enabled.
Following issues are facing :

  • Not able to build falcosecurity/falco-builder docker image getting error as
    "Cannot find a valid baseurl for repo: centos-sclo-sclo/ppc64le"
  • Not able to build falcosecurity/falco:test docker image, As the "falco/docker/local/Dockerfile" downloads gcc-6/5 and binutils pre-built packages. So Docker package test case is failed.

Issue
falcosecurity/falco#982
PR
falcosecurity/falco#932

Details about the discussion

  • Need to port the dockerfiles to support ppc64le platform.
  • Docker files should support latest OS having higher kernel versions with eBPF enabled. So we can
    use latest versions of gcc and binutils instead of downloading pre-built packages.

Discuss the rule engine versioning

What type of proposal is this?

/kind issue

Details about the discussion:

This Falco's issue propose to document the rule engine version against macros/rules it introduces or not.

Imho, first of all we should discuss how to approach the versioning.

I think @mstemm and probably also @KnoxAnderson should be active part of this discussion.

Test debugging hours

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue
/kind debugging-hours

Details about the discussion

Testing debugging hours integration

Implement HackMD

What type of proposal is this?

/kind issue

Details about the discussion

I am wondering if we want to implement the HackMD service for office hours? It saves us the time of going from Google Docs to Markdown, and I think Markdown is our goal here.

https://hackmd.io

Test

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue
/kind pr

Details about the discussion

Cute animals

/woof

Falco kiosk at Kubecon NA 22 - call for volunteers

Hi team - I need volunteers to help staff the Falco kiosk during Kubecon NA 2022 in Detroit.

Event dates:

  • Oct. 10/25: set up volunteers from 8am - 5pm
  • Oct. 10/26: staffing from 10am - 8pm
  • Oct. 10/27: staffing from 10am - 5pm
  • Oct. 10/28: staffing & breakdown from 10am - 4pm

Please sign up here

KC NA 22 - project meeting prep doc

https://docs.google.com/document/d/1dR7YjXC9D35aQ2mbqdq0UPB_ir70gYUJOHVI3vh1Yik/edit?usp=sharing
Sharing for transparency! This doc will be our prep doc for organizing the project meeting at Kubecon 2022.

  • We need to finalize the topics we want to address as a community
  • We need a moderator or two?
  • We need a few community members to take on a section of the agenda
  • What type of swag do we want to give away...
  • Other ideas or proposals dive into the doc link above and async collab w/me

Falco materials for Kubecon NA 2022

Hi team - I am creating materials for events that the community can leverage to help evangelize Falco. Please provide feedback and/or edits.

Poiana driving release process

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue

/kind pr
/kind debugging-hours

Community driven brand

Hi everyone,

We have had one of the companies that support Falco ask for some branding about Falco.

Primarily as a community they would like for us to answer

What value would a DevOps engineer find in Falco?

On the next office hours call can we talk about where we want to start tracking this work? I also will let the company that reached out about this know, that we would like them to be involved with drafting something here.

Standardized README.md files

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue
/kind pr
/kind debugging-hours

During the next office hours can we look at standardizing our README.md files?

Also should we look at re-writing some of these? Maybe on a live stream? Maybe at Kubecon?

If we make it easy for people to find what they are looking for, we can drive adoption greatly.

Falco unit testing

What type of proposal is this?

/kind issue

Details about the discussion
With falcosecurity/falco#686 - we introduced the
usage of the Catch2 to write tests for existing code and start going towards a more test driven style for future features.

We also have a reference PR containing some initial tests: falcosecurity/falco#692

We would like to discuss about contributing opportunities to test Falco features and on how to get onboard new features with this style.

Rebrand `office-hours` to `community`

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue

/kind pr
/kind debugging-hours

Decided on the repo planning call, we would like this repositories scope to expand beyond office hours.

Falco project meeting @ KC+CNC NA 2022

Hey team -
Opening an issue about the upcoming opportunities at Kubecon+CloudNativeCon NA 2022 in Detroit, MI.
This ticket is to kick off planning for the project meeting happening Oct. 25, 2022 @ xx:xx.

Falco project meeting (4 hrs)

Next steps:

  • start planning async
  • weekly updates at our community call on progress
  • maintainers - who would like to help plan and speak at project meeting?
  • community - attendance of who is at Kubecon and can support project meeting?

What are the topics we should discuss at the meeting?

How should we structure the agenda?

What other items do we need to coordinate:

  • food/drink
  • swag
  • presentation
  • invitation to the community (email)
  • invitation to the community (twitter)
  • invitation to the community (slack)

Introduce repository template + .github repo

What type of proposal is this?

/kind issue

Details about the discussion

I think we need to introduce a repository template for the whole falcosecurity organization.

Some features:

  • Be language agnostic
  • Contain a README.md
  • Contain a CONTRIBUTING.md
  • Contain a LICENSE file

Demo of the test grids' kernel builder

What type of proposal is this?

/kind debugging-hours

Details about the discussion

Wanted to show everyone a possible solution we can use to build kernels for the upcoming test grid.

The purpose is to gather feedback and make it a bit better and more stable afterwards.

One hackmd

On last week's call @fntlnz mentioned that we should use a single hackmd link.

I think we can just recycle the one from last week

Guidelines for contributing rules

What type of proposal is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind issue
/kind pr

Details about the discussion

We have an open issue on Falco on contributing guidelines: falcosecurity/falco#605 it would be cool to talk about those and see what others think.

teal-logo.png might be broken?

I'm making a presentation to introduce Falco to my company, and I wanted to embed official logos into the presentation. I cloned this repo and tried to insert all the images under the logo directory. The "primary logo" and "white logo" worked perfectly, but the "teal logo" showed a broken image. When I attempted to view the image in Firefox (by navigating to file://Path/to/teal-logo.png), I got the following error:

Screen Shot 2021-03-03 at 10 20 07 AM

I'm going to try to embed the current version of the logo below:

Maybe Broken Image

Do you want to change this to be a symlink to the primary logo?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.