Spinnaker Plugins: Extending...
summary
Shows a working plugins pathway for Spinnaker: Halyard downloads plugin jars, Orca loads them at startup, and a demo random wait stage (repo github.com/armory/stage-plugin) runs inside Orca returning random seconds so the system actually executes the plugin. Describes moving from brittle handwritten extensions toward PF4J for PF4J classloader isolation and well defined extension points, allows remote non‑Java services, requires Spinnaker 1.16+ and Halyard 1.23+, and notes UI and lifecycle gaps still being iterated.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:20What are They?
- 2:05Who Creates Plugins?
- 4:06Motivation
- 6:08Examples in Other Projects
- 12:08Modifying Spinnaker was Hard
- 14:06Stage Creation is Easy!
- 15:18How do I do this?
- 18:13Community Involvement
- 19:12In Spinnaker Today
- 20:52How Does it Work?
- 22:34Drawbacks
- 23:39Features? (Advanced)
- 26:52Frontend Plugins
- 29:26Remote Plugins
- 30:34PF4J
- 31:33Use Cases
related talks
22mSpinnaker Plugins by Example
24mSpinnaker Extensibility: A Journey
01h 52mPlugins Training Workshop
16mPlugins: An internals deep dive
10mMy Experience Creating an Orca Plugin for the First Time
01h 54mFirst-time Spinnaker Contributors Workshop
45mWorkshop: Extending Spinnaker via Custom Jobs
01h 21mGet Started with Plugin Development: A Github plugin for workflow dispatches