The largest community of platform engineers out there. Learn from leading DevOps experts. Connect with fellow platform nerds.
This community was born as a series of Meetup events in Berlin, Germany and Austin, Texas. It grew to much more than that in just a few months. We recently launched our Slack community, Platformengineering.org and this channel. More to come.
hello on min 26:15 you mention, ReBAC can be used to express ABAC or RBAC. My understanding is the other way around. You actually use ABAC to express ReBAC or RBAC.
This is the first time I have seen GitHub Actions being used as the Platform Orchestrator. We use Octopus Deploy, mainly because of its GUI, and its nailing of tenancy management. Till now, I haven't seen any useful information around how GA can do those things. Is it better to use Octopus over GA as the orchestrator?
CD implies CI, CI is part of CD, CD can't exist without CI. Without CI, CD is just... D. It isn't continuous. The "CI Kung Fu" is not a problem of Jenkins or any other automation tool, it is a problem with GitOps and the async nature of Argo/K8s. Synchronous GitOps tools don't require those web hooks to talk back to Jenkins. I really like Kargo but it feels like it is trying to blame everything else instead of saying "Hey, look, we improved the Argocd experience, now we can have environment promotion mechanisms".
Thanks for sharing. Today, I see companies and teams adopting many platforms to try to solve the same problem and losing focus because they learn only 10% of this platform and change to another, thinking they will find someone who makes all they need.
Very insightful. 👍 Thanks! It was more like a DevOps tutorial from Kelsey, than a Q&A -- definitely useful for smaller companies, not so much for bigger enterprises.
Your presentation was incredible! These issues often arise when teams and companies scale, yet they are rarely discussed. There is still so much to improve in platform development
The analogy to car platforms is a bit strained. It probably aligns to the 'independent instances' in the mapping slide, but even then car manufacturers generally customize the platform slightly for every car model. Anyone who has tried a similar approach, deploying a slightly customized version of a platform for every client, has learned how unmanageable that becomes. Software development started out by acting like it was similar to physical engineering, and that caused a lot of issues, which were really only overcome in the Agile revolution - which acknowledged that developing software was fundamentally different.
Good video and discussion. I don’t understand the need to create a new format. Why not use terraform and use a custom provider. That would lessen the learning curve and reduce the number of components in the tool chain. This also assumes all required components are available for developers. That’s very unlikely and a way for teams to contribute back to this library is required. Introducing a new tool is very similar to the Netflix problem. You have to convince them it’s worth doing. My experience (and yours) is that’s not a very likely path to success.
I think "Value Of" is important and different than ROI. "Value Of" has been a significant effort I have focused on in the last year and I think differs from ROI. They support different business modes. Public and private sector have to deliver on different financial frameworks. I think Mr. Rizzo is onto a topical difference here.
If you stop using "capabilities" and use "business need" or just "need", might have avoided all those mistakes. Words help to form ideas. Business doesn't NEED capabilities, business NEEDS to do certain stuff. It's almost same, just simpler, and helps to share with everyone what needs to be atchieved. Agile 101. Express business needs in the following atricture: As a ... I need /want to ... So that ... And pretty much all you mistakes could have been avoided.
Fully agree - one of my mentioned lessons learned: 10:30 :) I am not english-native, so in this case using "capabilities" does not usually mean my attitude/brain is corrupted. The whole speech I've given was about the needs recognition, in fact. Thanks for the comment!
