Hi! Welcome to the Spinnaker Newsletter, your source for info about the project and community. We’ll focus on news for Spinnaker users, operators, and contributors.
We just wrapped an incredible Summit. In case you missed it (or want to replay each delicious moment) here’s a reflection from the Armory blog and a video of Isaac Mosquera’s keynote , along with recaps from OpsMX highlighting 5 key takeaways , as well as technical and feature takeaways .
Attendees had numerous opportunities to connect, and high-quality sessions to choose from. Apart from helpful accounts of enterprise Spinnaker adoption journeys, we also hosted discussions on:
And much more! Access the slides from all event presentations here . Look out for video, to be posted on YouTube and announced in Spinnaker Slack . Important discussions about the roadmap and future of Spinnaker also took place. Read more on that below!
All eyes were on the 2020 roadmap at the Summit, with themes of managed delivery, operator and developer experience, cloud-nativization, community, and runtime support on the brain. Dev workflows for those using K8S, the AWS clouddriver, Cloud Run, and Tekton figure prominently in H1, as do modern tools for managing Spinnaker: config-as-code approaches to provisioning, auto-generated docs, cloud integration tests, Prometheus monitoring, and more.
Read the release highlights . Notable feature adds include baseline git repo artifact support, and Kustomize support to leverage that new artifact type. In addition, Spinnaker now proudly supports Kubernetes’ new kubectl-initiated rolling restart capability, as well as isolation between multiple K8S V2 accounts. Also added: a more flexible authorization model which allows Fiat to accept and resolve permissions from various sources.
We’ll highlight Spinnaker evangelism here as users share love on the interwebs. In a delightful new Medium post, Serge Poueme discusses SAPs evaluation and adoption of Spinnaker . He praises the “digestible UI on the surface and .. controlled environment in the back end,” as well as the interoperability with Jenkins, Slack, and GitHub his teams enjoy as they take a developer-self-service approach to CD. My fave quote:
“When William found a bug, he determined the root cause and then proposed a fix via a pull request. Spinnaker responded swiftly, then provided further documentation for him to contribute to the project — another well-deserved high five to Spinnaker for being open source!”
You can say that again, Serge! He also boldly shares his feature requests, including a Halyard API for automation changes to Spinnaker instances, and better security, particularly around Docker image sourcing. His top request? Better documentation. Let’s put that on the agenda of the upcoming hackathon!
As we invite users and contributors into the community, opportunities to unite on clear project goals and milestones arise. The TOC, SIG leads, and community advocates are working improve the Spinnaker contributor experience. If you have feedback about this, please share it at your next SIG meeting, and/or in the #community channel on Spinnaker Slack . Look out for experiments that aim to organize issues and improve your experience in advance of our first hackathon. Also: please be un-shy in filing issues. We have a particular need for first-hand “end-user”/developer feedback. Don’t be afraid to engage!
Netflix and Google donated Spinnaker to the [Continuous Delivery Foundation]https://go.armory.io/cdf) in March. The Foundation aims to tell the world the crucial story of CD, and to foster a vibrant community around it. From Spinnaker’s perspective, we want to improve collaboration among open-source partners, considering the importance of solution interoperability and clarity to our shared users (Jenkins, in particular, comes to mind here).
Check out the strategic goals the CDF has charted for us:
Looking forward to working with the amazing Spinnaker community to realize these!