Skip to content

brigadecore/brigade

Repository files navigation

Brigade 2: Event-based Scripting for Kubernetes

build slack

Brigade 2 has been lovingly re-engineered from the ground up. We believe we've remained faithful to the original vision of Brigade 1.x, and as such, much general knowledge of Brigade 1.x can be carried over.


But we've also learned a lot from Brigade 1.x. Brigade 2 has been designed, explicitly to reduce the degree of Kubernetes knowledge required for success. While Brigade 1.x was hailed as "event driven scripting for Kubernetes," Brigade 2 is "event driven scripting (for Kubernetes)." Moreover, great care has been taken to improve security and scalability, and with our all new API and complementary SDKs, we're also lowering barriers to integration.

We hope you'll enjoy this product refresh as much as we are.

Getting Started

While comprehensive documentation remains a work in progress, our quickstart is well-polished and we refer users wishing to test drive Brigade 2 to that documentation.

The Brigade 2 Ecosystem

Brigade 2's all new API lowers the bar to creating all manner of peripherals-- tooling, event gateways, and more.

Gateways

Gateways receive events from upstream systems (the "outside world") and convert them to Brigade events that are emitted into Brigade's event bus.

The Brigade GitHub Gateway, in particular, is already utilized extensively by the Brigade team in combination with Brigade 2 to implement the project's own CI/CD. This is our favorite gateway at the moment because it also reports event statuses upstream to GitHub, making it a true showcase for what can be done with gateways.

Monitoring

Brigade Metrics is a great way to obtain operational insights into a Brigade 2 installation.

Chaos Engineering

The Brigade team is utilizing Brigade Noisy Neighbor to keep our own internal Brigade 2 installation under a steady load. We hope the larger event volumes than what we generate on our own will help us to identify and resolve bugs sooner.

SDKs

Use any of these to develop your own integrations!

Contributing

The Brigade project accepts contributions via GitHub pull requests. The Contributing document outlines the process to help get your contribution accepted.

Support & Feedback

We have a slack channel! Kubernetes/#brigade Feel free to join for any support questions or feedback, we are happy to help. To report an issue or to request a feature open an issue here

Code of Conduct

Participation in the Brigade project is governed by the CNCF Code of Conduct.