Learn Cloud Native & CNCF - Platform Engineering & Internal Developer Platforms

#Introduction

In episode 17 we saw how AI was brought into cloud native. Episode 18 discusses a trend just as big and closer to an engineer's daily life: platform engineering. This trend changes how organizations build and provide infrastructure for their developers.

For years, infra teams acted as gatekeepers: developers had to queue for servers, access, or deployment permissions. Platform engineering flips this model — infrastructure is provided as a product, complete with self-service paths developers can use without waiting for anyone.

By the end of this episode you will understand the concepts of platform engineering and IDP, know CNCF's role through TAG Platform Engineering and its certification, and see the projects that serve as its building blocks.

#What Platform Engineering Is

#From Ops to Product

Platform engineering is the discipline of designing, building, and maintaining internal platforms — a set of tools and services that development teams use to deliver software. The main change lies in the way of thinking: the platform is treated like a product with users, needs, and a roadmap.

The consequences of this mindset are large. Platform teams no longer measure success by uptime alone, but by how fast and easily internal developers can ship features. The satisfaction of "internal customers" becomes the primary metric.

This shift also changes team structure. Instead of many ops teams handling infrastructure separately, one platform team emerges serving all product teams. It's more efficient, and it opens attractive new career paths for engineers.

#IDP: Internal Developer Platforms

The core product of platform engineering is the IDP, or Internal Developer Platform — a collection of services that provides everything developers need in one unified experience: cluster access, development environments, pipelines, monitoring, and documentation.

An IDP isn't a single tool but a layer unifying many technologies — often CNCF technologies. The job of platform engineering is to assemble and manage this layer so developers no longer need to understand the details behind it.

#Golden Paths and Self-Service

#Golden Path: The Recommended Route

A golden path is the development route recommended by the organization — a combination of technology standards and patterns proven to be safe and efficient. Developers may deviate from this path, but the main route must always be the easiest to take.

The golden path concept balances freedom and standardization. Developers aren't forced to use one technology, but if they choose the standard route, everything is already available: templates, access, and support. The result is speed without sacrificing security.

One important principle here is "treat exceptions as products too". If many teams deviate from the golden path for the same reason, that's not developer failure — it's a signal that the platform needs fixing. Deviation data is valuable feedback.

#Self-Service as the Goal

The ultimate goal of platform engineering is self-service: developers can get environments, create services, and ship deployments themselves without tickets or manual approval. Every click or command that removes a queue is a win for productivity.

In the cloud native world, self-service is built on top of Kubernetes APIs and tools like Backstage, Crossplane, and Argo — which we'll discuss shortly. The key is a friendly interface over powerful complexity.

It's worth emphasizing: self-service doesn't mean no control. Access is still governed by policy and approval for major decisions. What's removed is queuing for routine things, not oversight for high-risk ones.

#CNCF's Role in Platform Engineering

#TAG Platform Engineering

CNCF responded to this trend officially by forming TAG Platform Engineering — a forum for sharing practices, setting standards, and discussing the future of internal platforms. This TAG is also the birthplace of guidance on building IDPs with cloud native technology.

The existence of this TAG signals that platform engineering isn't a passing fad, but a direction the industry believes will last. It serves as a bridge between vendors, practitioners, and the projects that build platforms.

#The Platform Engineering Certification

As the field matures, CNCF launched the Platform Engineering certification in 2025. This certification sets a standard for skills that previously lacked clear definition: designing platforms, managing golden paths, and measuring developer experience.

For those interested in this career path, the certification is a useful competency map — both for learning and for proving ability in front of employers.

#Related Projects Worth Knowing

#Backstage, Crossplane, and Others

Several CNCF projects are the main building blocks of IDPs:

• Backstage — a developer portal unifying all tooling in one interface.
• Crossplane — a control plane for provisioning cloud resources via Kubernetes.
• Dapr — a runtime for easily building distributed applications.
• Argo — workflows and continuous delivery that form the backbone of delivery.

These four projects show the typical platform engineering pattern: using proven components, then unifying them into a complete developer experience.

#Trying Backstage

To see what a developer portal actually looks like, you can install Backstage with Helm:

helm repo add backstage https://backstage.github.io/charts
helm repo update
helm install backstage backstage/backstage -n backstage --create-namespace

The helm repo add command adds the Backstage chart repository, then helm install installs it into a dedicated namespace. The installed Backstage will give you a sense of the interface developers typically use to find services and access documentation.

#Skills for Becoming a Platform Engineer

#A Technical-Product Combination

Becoming a platform engineer demands a rare combination: deep technical understanding of cloud native, and product understanding of internal users' needs. You must be able to choose tools, design experiences, and measure success.

For those who are learning, start by mastering Kubernetes as the foundation, then learn tools like Backstage and Crossplane, and don't forget to train the ability to listen to user needs — because good platforms are born from empathy, not just technology.

Platform engineering also opens one interesting opportunity: it combines the technical and communication sides in one role. For those who enjoy both, this is one of the most satisfying career directions in the cloud native world today.

#Closing

Episode 18 dissected platform engineering: the shift from ops to product, the IDP and golden path concepts, the role of TAG Platform Engineering and its certification, and projects like Backstage, Crossplane, Dapr, and Argo that are the building blocks of modern platforms.

Key takeaways:

• Platform engineering treats infrastructure as a product with internal users.
• An IDP unifies all developer needs in one experience.
• The golden path is the standard route that's easiest to take.
• Self-service is the primary goal of platform engineering.
• TAG Platform Engineering and its certification signal the field's maturity.
• Backstage, Crossplane, Dapr, and Argo are common IDP building blocks.

In episode 19 we'll close the trends phase with three topics: GitOps, edge, sustainability, and emerging technologies — Argo CD and Flux as GitOps standards, KubeEdge for the edge, and CNCF's efforts to reduce cloud native's carbon footprint.