Thoughts from KubeCon on Konflux-CI
4 views
Skip to first unread message
Andrew McNamara
Nov 18, 2025, 4:05:49 PMNov 18
to Konflux CI
I was thinking a lot about Konflux-CI at KubeCon last week. So much so that I think the content is too long to send directly in an email. I have included the introduction to the trip report in the email below, but feel free to review the document for more details:
---------
I had the pleasure of being able to attend KubeCon last week. While I attended a couple of interesting talks, I am not going to focus on that here. Instead, I would encourage you to view the schedules (co-located events; kubecon), find interesting talks, and watch recordings once they are posted. Instead, I want to focus on the hallway conversations, specifically how they made me think about the direction of Konflux-CI.
I really enjoy working within the supply chain and Konflux spaces and I want to share what we have done more broadly. I truly believe that what we have done can be an example for others that are exploring their own software supply chain options, especially if they want to achieve a balance between flexibility and security. I would love for us to be recognized as public leaders in this space!
While others may share in this desire as well, I have received caution that we shouldn’t push to be vocally public too early. I think that we can still talk about individual aspects of our tooling (policy evaluation, trusted artifacts, accurate SBOMs, leveraging provenance and SBOMs, etc.), but if we try to bring people to Konflux in its entirety, we really only have one chance to entice each person to stick around. If they encounter usability challenges, they will likely leave with a bad experience and not come back. I have heard people asking about why we are focusing on external users before we have them. THIS is why – so that we can clearly show people how Konflux can solve their problems from the beginning, keeping them engaged.
I have laid out the biggest gaps that I see in Konflux-CI today and how we can work to address/close them. By focusing on better integration of community standards and tools, we will allow new community members to more easily relate their current knowledge into our system so that they have a jumping off point to continue exploring.
I really enjoy working within the supply chain and Konflux spaces and I want to share what we have done more broadly. I truly believe that what we have done can be an example for others that are exploring their own software supply chain options, especially if they want to achieve a balance between flexibility and security. I would love for us to be recognized as public leaders in this space!
While others may share in this desire as well, I have received caution that we shouldn’t push to be vocally public too early. I think that we can still talk about individual aspects of our tooling (policy evaluation, trusted artifacts, accurate SBOMs, leveraging provenance and SBOMs, etc.), but if we try to bring people to Konflux in its entirety, we really only have one chance to entice each person to stick around. If they encounter usability challenges, they will likely leave with a bad experience and not come back. I have heard people asking about why we are focusing on external users before we have them. THIS is why – so that we can clearly show people how Konflux can solve their problems from the beginning, keeping them engaged.
I have laid out the biggest gaps that I see in Konflux-CI today and how we can work to address/close them. By focusing on better integration of community standards and tools, we will allow new community members to more easily relate their current knowledge into our system so that they have a jumping off point to continue exploring.
Red Hat
He / Him / His
Reply all
Reply to author
Forward
0 new messages