[Community] Developer experience on Kubernetes (as a platform) - Blog

loujaybee commented 10 months ago

Contribution Description

I am creating a webinar for work (source). I believe content of the webinar would make for a great CNCF branded blog post. I also want to harden my understanding of the technology to make sure the content quality is as high as possible.

A first draft of the content will be ready next week in preparation for the webinar run date of 15th February 2024.

Problem statement

Kubernetes is complex, and biases for solving "problems in production". Many platform teams can find themselves struggling to create the surrounding developer experience for their internal platforms. An ecosystem of tools, patterns and solutions has emerged around the problem, but they are often not commonly known, understood or shown how to combine them to improve end-user developer experience when your platform is running on Kubernetes.

Early draft content

The description of the webinar content includes:

Build a platform around your Kubernetes cluster(s) that prioritises developer experience
Avoid “works on my machine” and configuration drift problems with Kubernetes
Design developer experience for fast feedback (not 30 minute CI builds).
Go from a single local docker container, to multi-container to pre-prod preview clusters.
Use proxies like Telepresence, MirrorD to connect local services to a Kubernetes cluster.
Considerations on internal developer portals like Backstage. ...etc

Previous message in the CNCF Platform Group - and link to thread.

Developer experience on Kubernetes (as a platform) - I’ve been going deep on the topic of end-user developer experience on Kubernetes, including the many, many tools that can form a part, or a whole solution here. A few people expressed they’d like to see a whitepaper on this. Whilst I could take a swing myself, that feels like a topic very much in this groups wheelhouse. If anyone is interested, I’d be keen to explore what this could look like. I see scattered content on the topic, I’m yet to read anything that’s truly comprehensive…

Related Working Group (WG)

Platforms

Contribution type

Blog (Default)

Why TAG App Delivery?

Very Platform related.

Related projects/technologies

https://mirrord.dev https://kubernetes.io https://www.telepresence.io https://backstage.io https://score.dev

Affiliation disclosure

I work for (Gitpod). If relevant the topic could cover Cloud Development Environments (CDEs), but this content is not intended to centre around CDEs.

Additional collaborators

Antoine Bermon, Cat Morris, Abby Bangser, Saim Safdar,

Additional information

No response

loujaybee commented 10 months ago

📆 Discussion / brainstorming meeting scheduled next week.

Scheduled a 30 Minute open invite to start the discussion - meeting link.

Time: 4:00pm - 4:30pm, Wednesday, January 31, 2024 - UK, Ireland, Lisbon Time.

Current attendees: Antoine Bermon, Lou Bichard, Saim Safdar.

abangser commented 10 months ago

I think this is great @loujaybee !

It sounds like you have a lot of momentum behind this for a webinar and that you could repurpose for a blog post. In general community blog posts are encouraged to be author led so long as they abide by the community guidelines. But of course authors can choose to collaborate as much as they would like with the group and that would be great.

One thing I would recommend for this post in particular is to keep an eye on the webinar and determine if there is a natural split for multiple blog posts. I suspect there may be a couple here and that they can help you (and the group) suss out if there is a larger scale white paper or reference architecture here that can grow from them.

ebcarty commented 10 months ago

@abangser are there any existing reference architecture(s)? I believe cnoe-interest is working on one (but perhaps focused on AWS).

Rotfuks commented 10 months ago

Really interesting topic and I'd like to join in on the discussion.

Last year I already wrote a blog post on how to Maximize Value with Kubernetes-as-a-Product by shifting the focus to the enduser. It's way less technical and looks more on the exploration and product side of things but I guess that might be a helpful perspective here as well.
But I also recently did a Telepresence Introduction 1pager for a german print magazine, so I also have some opinions there :laughing:
What do you think, @loujaybee ?

abangser commented 10 months ago

@ebcarty great question!

There are definitely reference architectures including CNOE, BACK, KubeFirst, and I am sure many more. Though I am not sure that is the angle @loujaybee is going with this as those are more about the low level tools. That being said, I am looking forward to hearing more and very well could be good to explore those directions!

loujaybee commented 9 months ago

Goal: - We are driving towards a first blog post to publish for the CNCF covering this topic.

Update: We had an introductory call in the working group where we spoke about Kubernetes and Developer Experience in a very broad and open sense. As there are lots of topics that come under "developer experience and kubernetes". I spoke with @abangser and we agree'd to try and tighten the scope of the discussions to make it easier to collaborate.

Scope: - This blog post: config drift causes a painful death for developers is a great framing of the problem space.

Strawman: I'm attaching here a strawman that lays out some different "patterns" for working with Kubernetes and resolving challenges with developer experience. Publishing a refined variation of this would be a good first goal here.

Next steps: - I’ll schedule another call in a week, or so. I'm presenting the content in a webinar on Wednesday (join if you'd like). I’ll continue my own research until then. If anyone wants to chat 1-1 this or next week, here’s my calendly.

Thanks for all the inputs so far ! Let's continue the discussion here async if needed, too! 👇

loujaybee commented 9 months ago

@abangser One thing I would recommend for this post in particular is to keep an eye on the webinar and determine if there is a natural split for multiple blog posts. I suspect there may be a couple here and that they can help you (and the group) suss out if there is a larger scale white paper or reference architecture here that can grow from them.

Yep, agree! I'm publishing two at work, one articulates this issue of "configuration drift" (Similar to the blog post above "Warning: config drift causes a painful death for developers"). And another that talks about patterns this blog post covers similar content. We can re-use some of that. I'd suggest for here we go straight for the "patterns" type post, as hopefully the CNCF audience is familiar with the problem and less of that preamble will be needed.

loujaybee commented 9 months ago

@Rotfuks Last year I already wrote a blog post on how to Maximize Value with Kubernetes-as-a-Product by shifting the focus to the enduser. It's way less technical and looks more on the exploration and product side of things but I guess that might be a helpful perspective here as well.

For sure, please share here, those seem very related !

Rotfuks commented 8 months ago

Heya @loujaybee! Finally managed to rework the blog post, here's the new version I talked about: https://www.giantswarm.io/blog/maximizing-value-with-kubernetes-as-a-product-fulfilling-the-promise-of-the-cloud

cncf / tag-app-delivery