Whats new in brigade 2

1. Event-Driven Scripting
for Kubernetes
Kent Rancourt
Senior Engineer – Microsoft
kent.rancourt@microsoft.com

2. What is an
OS?
A program that, after being initially loaded
into a device, manages all the other
programs.

3. Kubernetes as
a “Cluster OS”
An OS manages processes on a device.
Kubernetes manages containers in a cluster.

4. Traditional
Shell Scripting
Flow control that wraps the execution of
processes, but is not opinionated about what
the processes do, or how they run.

5. Cluster Shell
Scripting
Flow control that wraps the execution of
containers, but is not opinionated about what
the containers do, or how they run.

6. ► Asynchronous, event-driven scripting
► Chains together containers to create
workflows
► Uses Kubernetes as workload execution
substrate
► Users do not have to interact with
Kubernetes directly

8. Use Cases
Anything you might like to automate:
► CI / CD
► GitOps
► ChatOps
► Code scans / security audits
► Report generation
► And more…

9. Events
► Originate from external systems
► Indicate something has occurred
► Enter Brigade via event gateways

11. Some
Example
Gateways
► Bitbucket
► GitHub
► CloudEvents 1.0
► Slack
And custom gateways are easy to create.

12. Example
Event

13. Projects
► User defined
► Subscribe to events
► Define workers to handle events

15. Workers
► Embed JavaScript or TypeScript or…
► Include git coordinates for a script
► Run in a container
► Handle events
► Either directly in script or...
► May coordinate multiple jobs to
implement complex workflows

16. Project with
Embedded
Script

17. Project with
Script from
a Git Repo

18. Jobs
► Optionally created by workers to handle
discrete tasks
► Can be executed in serial or concurrently
(subject to scheduling constraints)
► Run in containers
► Based on any OCI image
► ”Sidecar” containers supported

19. Example
Jobs

20. Demo Time

21. Other
Features
► Git integration– build and test source
code
► Shared volumes– pass artifacts from job to
job
► Configurable limits:
► Max concurrent workers
► Max concurrent jobs
► Fair scheduling
► User authentication options:
► Any OpenID Connect identity
provider
► GitHub

22. Ecosystem
► Gateways
► Azure Container Registry
► Bitbucket
► CloudEvents 1.0
► DockerHub
► GitHub
► Slack
► More to come…
► Monitoring
► Brigade Metrics
► Chaos Engineering
► Brigade Noisy Neighbor
► SDKs
► Go
► JavaScript / TypeScript
► Rust (WIP)

23. Comparison
to Argo
Brigade and Argo address similar use cases and
both model workflows as assemblies of containers,
but they approach the problem space differently:
► Argo:
► Emphasizes workflows.
Events are an add-on (Argo Events).
► Is fully k8s-native.
Workflows are Kubernetes resources.
► Brigade:
► Emphasizes events.
Events do not describe workflows -- they only indicate something
occurred. Subscribed projects handle events as they see fit.
► Uses k8s as an implementation detail.
Workflows are scripted and tooling fully abstracts Kubernetes, so
teams can build automation that executes in Kubernetes without
being experts – and without every team member having direct
access to the cluster.

24. Architecture

25. Logical
Architecture

26. Physical
Architecture

27. Thank You!

28. Resources
► Web site: https://brigade.sh
► QuickStart: https://quickstart.brigade.sh
► GitHub: https://github.com/brigadecore/brigade
► Twitter: @brigadecore
► Slack: https://slack.brigade.sh

29. Typical
Deployment

30. Q&A