8:18 missing middle

Pure gold. Thanks Mallory!

Crossplane is crap. Great intention, stupid results.

Thank you for awesome talk. Greetings from 🇩🇰

That are all cool things, though not sure it's necessarily new...

Oh the sniffling. Getting past that the info was good and I appreciate it

Lovely to see Suresh and Ramesh Together 😊

Wow

❤❤❤

Awesome talk, Luca, learned a lot with you! Thanks for the fishes!!

I prefer Tofu for infrastructure state management outside of Kubernetes and ArgoCD for in-cluster state synchronization. Kubernetes-centric architectures like Crossplane seem to over-credit Kubernetes, extending its use beyond its primary purpose as a container orchestrator. That said, great talk on platform engineering, especially the first part about self-service IDPs!

Great presentation! Short, succinct, and straight to the point. Really appreciated the clarity and focus!

Nice video

Thank you for hosting me!

Confirmed to me that K8s networking is a disaster.

Came here to understand something. now going somewhere else to understand this video.

If we can have links for recordings and presentation that Ajay is talking about that will be super helpful

Thanks for this demo.. checking out the demo section again... so if I have backstage and score, what value does having humanitec provide? I would like to understand it from POV of "This is what you would need to do without humanitec vs if you have humanitec... all these steps can be reduced"

Problems with Backstage and the netflix tool announced in Pcon22... ---->lots of "solution salad"---demo. I would need to look at the whole video again but would be nice if the speaker just says "this is what my demo architecture is: Backstage, code repo in TF etc..) not faulting the technical skills just the presentation of this with lot of back and forth.. I totally didn't get the part of the graph based approach before the demo? Is the demo using a graph based approach? or not?

Trying to follow along... the flow of this video is confusing... it repeatedly highlights the problem with backstage and then then the top item in the demo is err.. backstage? would love to see the problem and the solution as am lost if the demo is the recomended solution or if is highlighting problems with backstage!

Thank you, Charity, strong points to consider

I couldn't find Mallory's "DevOps is dead" talk, just from other people. But I did find a "DevOps ain't dead" from her 😅 Could you share the link to that talk, please?

Nice content, companies lose the way easily without correct instructions like this video.

(27:54) I like how easy it looks to upgrade postgres from v14 to v15 with just 1 line of code. That might be true for ephemeral resources, but your production db has had data created into it for weeks, months or years and won't be easy to upgrade without causing headache. Update one file? I don't think so...

Came here to learn this role I will be promoted from Technology Production Specialist to Platform Engineering.

Thanks for sharing experiences in a simple way.

keep it up man.... don't let views demotivate you.

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.

Very impressive and relevant and realistic... introductory talk.

Super useful summary, thanks

Thanks for share your sucess path.

Great session with insightful questions and well crafted answers. Thanks for sharing!

non sense video, love it

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?

Very good tech demo Karan🎉. Did you get the chance to look into docker cache in kubernetes? If you have any solution please add one vedio. Thank you.

this is honestly one of the greatest conversations on the platform subject that I have ever seen

Here are the slides: docs.google.com/presentation/d/10vedI-8cPJS5MOH3jQ6MfKrB8u8c8ZB83sQ04Mv09ec/edit?usp=sharing

Can anyone share a link for "modernizing the developer runtime" talk that ben mentions at 9:03?

Very nice insights. Thanks for that!

We can use Victoria metrics effectively to replace Prometheus-operator to manage multi-cluster seamlessly. If I have an opportunity I will explain

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".

Great webinar and content! Pretty crazy to see an IDP at scale! 🔥

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.

Really an interesting and insightful talk

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

Hlo plz help me

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.

Who is Owen 😂