Plugin system - progress tracker

[leogr]

Motivation

Since the plugin system comprises several moving parts and many actions need to be performed in the correct order, I created this issue to keep track of their progress. So, what better place than the evolution repository for that? 😸

Overview

Briefly, before releasing the plugin system feature, the following must be completed and incorporated into our GitHub organization:

• the Plugin System proposal, already accepted
• the Plugin System support in libscap and lipsinsp, in progress
• the Plugin System feature in Falco (that depends on the previous point), in progress
• the Golang SDK to ease the writing of plugins in Golang, as foreseen by the proposal, inital draft ready
• the Plugin repository where concrete plugin implementations will live
• the official Plugin Documentation to be included in the Falco's website, draft ready

TODO list

Some tasks are needed to get the desidered results. Moreover, some of them depend on others that need to be worked on before. So, here is the full task list in the expected order:

• Proposal accepted
• Add plugin support to https://github.com/falcosecurity/libs, all relevant PRs need to get merged in (WIP here 👉 https://github.com/falcosecurity/libs/tree/new/plugin-system-api-additions, TBD list PRs here)
• Move https://github.com/mstemm/plugin-sdk-go/ to the Falcosecurity org
  • [ ] (maybe) Add correct circleci secret to circleci webhook (We'll use prow for builds instead)
  • [ ] (maybe) Add a circleci deploy key (We'll use prow for builds instead)
• Create an OWNER file for the plugin-sdk-go repository
• Configure the repo and set up the Prow (@poiana) workflow (PR Add plugin sdk go jobs test-infra#515)
• Document that the plugin-sdk-go repository has been adopted as an incubating project (PR Add falcosecurity/plugin-sdk-go as an incubating project #104)
• Make sure plugin-sdk-go go docs are available at pkg.go.dev
• Add plugin support to https://github.com/falcosecurity/falco, all relevant PRs need to get merged in (TBD, list PRs here)
• Move https://github.com/mstemm/plugins to the Falcosecurity org
  • [ ] (maybe) Add correct circleci secret to circleci webhook (We'll use prow for builds instead)
  • [ ] (maybe) Add a circleci deploy key (We'll use prow for builds instead)
• Create an OWNER file for the plugins repository
• Configure the repo and set up the Prow (@poiana) workflow (PR Add plugins jobs test-infra#516)
• Document that the plugins repository has been adopted as an incubating project (maybe we want to promote this repo as "official" directly?) (PR Add falcosecurity/plugins as an incubating project #105)
• Make the first release of plugin-sdk-go with the version equals to 0.1.0 (DO NOT do that until we assume the APIs are stable enough)
• (maybe) Make the first release of all (or some) plugins included in the registry
• Release a Falco version that includes the plugin's support (the plugin system will become official from this point on)
• Add the plugin documentation to https://github.com/falcosecurity/falco-website (WIP here 👉 Add plugins docs falco-website#493)

/assign @leogr
/assign @mstemm

[leogr]

Hey @mstemm

I have added some suggestions to your test-infra PRs. Also, I have made two PR to add a notice in both projects' README to reflect their current status.
PTAL 🙏

[leogr]

I believe that everything is ok now 😃

so
/close

[poiana]

@leogr: Closing this issue.

In response to this:

I believe that everything is ok now 😃

so
/close

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.