{"id":4839,"date":"2026-01-06T20:51:03","date_gmt":"2026-01-06T19:51:03","guid":{"rendered":"https:\/\/gokhan-gokalp.com\/?p=4839"},"modified":"2026-01-06T20:56:40","modified_gmt":"2026-01-06T19:56:40","slug":"devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro","status":"publish","type":"post","link":"https:\/\/gokhan-gokalp.com\/tr\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/","title":{"rendered":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO"},"content":{"rendered":"

In the first two parts of this DevEx<\/em> series, I tried to show how golden paths in Backstage<\/em> can enable developer self\u2011service without chaos and how extending the catalog into copilots<\/strong> with MCP<\/em> servers transforms discoverability into a conversational<\/strong> experience. Both of these steps were about reducing friction and giving developers paved roads to move faster while still staying compliant.<\/p>\n

Back in the first article, I also touched on the broader idea of IDPs,<\/em> how organizations often build them with tools like Crossplane<\/em>, Tofu<\/em> Controller<\/em>, Argo CD<\/em>\u00a0and OPA<\/em> on top of Kubernetes, <\/em>that was also the stack I worked with in practice, powerful but not always the most approachable starting point for teams because of the complexity involved as I also stated in the first article.<\/p>\n

In this article, I want to focus on Azure Service Operator<\/em><\/strong> (ASO<\/em>) which provides a Kubernetes <\/em>native way to reconcile Azure<\/em> resources directly from manifests and when combined with Kubernetes Resource Orchestrator <\/strong><\/em>(KRO<\/em>), it becomes more streamlined to expose developer friendly abstractions without the heavy complexity of other stacks. While many organizations build IDPs<\/em> with different controllers and toolchains like Crossplane<\/em> or Tofu Controller<\/em>, using KRO<\/em> and ASO<\/em> in the Azure<\/em> ecosystem gives us a more minimal<\/strong> and practical<\/strong> path to build the IDP<\/em> platform foundation that is easy to approach and ready to grow.<\/p>\n

Lately, I have been experimenting with ASO <\/em>and KRO<\/em> and I really liked how much they simplify the experience. That is why I wanted to include this stack in the series as well. With Backstage<\/em> as the portal, KRO<\/em> and ASO<\/em> as the abstraction layer and the reconciliation engine, we can deliver a clean path where developers request what they need and the platform control plane provisions it automatically in Azure <\/em>in a simple, compliant way that scales.<\/p>\n

Let\u2019s Get Started with KRO and ASO<\/h1>\n

Now we have the motivation, so let’s get started looking at KRO<\/em> and ASO<\/em> and see how they work together in practice.<\/p>\n

KRO<\/em> provides us a Kubernetes<\/em> native way to define our own simple abstractions as custom resources (CRDs<\/em>) that encapsulate the logic we want to expose to developers along with any organizational standards and best practices. In essence, KRO<\/em> gives us the abstraction and orchestration layer. It lets us deploy multiple resources as a single unit but on its own it doesn’t provision anything.<\/p>\n

This is where ASO <\/em>comes into play. It acts as a reconciliation engine that actually provisions and manages the Azure<\/em> resources behind those abstractions. It lets us define Azure<\/em> resources as Kubernetes<\/em> custom resources. Together, these two tools give us an abstraction layer and a reconciliation engine that together form the backbone of a simple automation platform<\/strong> on Kubernetes<\/em>.<\/p>\n

Installing KRO and ASO on AKS<\/h2>\n

I will assume that we already have a running AKS<\/em> cluster, so we can jump straight into getting these two tools installed.<\/p>\n

First, we will start installing ASO v2<\/em> on the cluster. To keep things simple, we will follow the steps from the official ASO<\/em> documentation (Azure Service Operator<\/a><\/em>). First install cert-manager<\/em>, since ASO<\/em> uses it to issue and rotate certificates, then deploy ASO v2<\/em> itself with a specific CRD<\/em> configuration and finally configure a service principal or a managed identity that ASO<\/em> will use to authenticate against Azure<\/em>.<\/p>\n

<\/p>\n

That being said, let’s use the following helm<\/em> command to install ASO v2<\/em> along with the “resources.azure.com\/*;*app.azure.com\/*<\/em>” CRDs<\/em>\u00a0which are the only ones we need for this article series. By default, ASO<\/em> doesn’t install any CRDs<\/em> instead it allows us to choose which ones to enable via the “crdPattern<\/em>” parameter. For now, we will install the Azure Container Apps CRDs<\/em> since we will use them in our demo.<\/p>\n

helm upgrade --install aso2 aso2\/azure-service-operator \\\r\n    --create-namespace \\\r\n    --namespace=azureserviceoperator-system \\\r\n    --set crdPattern='resources.azure.com\/*;*app.azure.com\/*'<\/pre>\n
<\/p>\n
Once ASO<\/em> is installed, we should see its pods running in”azureserviceoperator-system<\/em>” namespace.<\/p>\n
\"\"<\/a><\/p>\n
At this point, ASO<\/em> alone lets us define and provision Azure<\/em> resources as Kubernetes<\/em> CRDs<\/em>. But when we add KRO<\/em> on top, its orchestration capabilities allow us to define opinionated, developer\u2011friendly abstractions that orchestrate everything behind the scenes. Without KRO<\/em>, we wouldn\u2019t be able to orchestrate multiple resources behind a single, simplified abstraction.<\/p>\n
So, let\u2019s follow the same approach and install KRO<\/em> on the cluster as well by using the steps from the official KRO<\/em> documentation (Installing kro<\/a><\/em>).<\/p>\n
With installation of KRO<\/em> alongside ASO<\/em>, we now have the minimal backbone of an Azure<\/em> focused IDP<\/em>. From this point, our AKS<\/em> cluster becomes a lightweight, centralized platform orchestrator.<\/p>\n
Let’s Create a Simple, Orchestrated Azure Resource Template with KRO and ASO<\/h2>\n
Now that both ASO<\/em> and KRO<\/em> are installed, we can create a small abstraction that provisions a few Azure<\/em> resources as a single unit. This follows the same idea behind “golden templates<\/em>” we explored earlier in this series. Instead of asking developers to stitch together multiple files or understand every Azure<\/em> resource, we expose a single, opiniated interface that hides all of that complexity.<\/p>\n
To keep things simple, we will create a simple abstraction that sets up a “Resource Group<\/em>“, an “Container Apps Environment<\/em>” and a “Container App<\/em>” in an Azure<\/em> environment. We can think of this as a lightweight, serverless starter kit<\/strong> with built\u2011in best practices for the platform.<\/p>\n
So, to build this starter kit, we will use “ResourceGraphDefinition<\/em>” in KRO, <\/em>this is where we describe the high level abstraction, the template itself. It\u00a0is the core API<\/em> in KRO<\/em> for defining CRDs<\/em> that orchestrates multiple resources. It links the ASO<\/em> resources and ensures everything is provisioned in the right order.<\/p>\n
apiVersion: kro.run\/v1alpha1\r\nkind: ResourceGraphDefinition\r\nmetadata:\r\n  name: aca-starterkit\r\n\r\nspec:\r\n  schema:\r\n    apiVersion: v1alpha1\r\n    kind: ACAStarterkit\r\n    spec:\r\n      location: string\r\n      image: string\r\n      cpu: string | default=\"0.25\"\r\n      memory: string | default=\"0.5Gi\"\r\n      targetPort: integer | default=80\r\n    status:\r\n      resourceGroupName: ${resourceGroup.status.name}\r\n      appFqdn: ${containerApp.status.configuration.ingress.fqdn}\r\n\r\n  resources:\r\n    - id: resourceGroup\r\n      template:\r\n        apiVersion: resources.azure.com\/v1api20200601\r\n        kind: ResourceGroup\r\n        metadata:\r\n          name: \"${schema.metadata.name}-rg\"\r\n        spec:\r\n          location: \"${schema.spec.location}\"\r\n\r\n    - id: containerAppsEnv\r\n      template:\r\n        apiVersion: app.azure.com\/v1api20240301\r\n        kind: ManagedEnvironment\r\n        metadata:\r\n          name: \"${schema.metadata.name}-env\"\r\n        spec:\r\n          owner:\r\n            name: \"${resourceGroup.metadata.name}\"\r\n          location: \"${schema.spec.location}\"\r\n          workloadProfiles:\r\n            - name: Consumption\r\n              workloadProfileType: Consumption\r\n\r\n    - id: containerApp\r\n      template:\r\n        apiVersion: app.azure.com\/v1api20240301\r\n        kind: ContainerApp\r\n        metadata:\r\n          name: \"${schema.metadata.name}\"\r\n        spec:\r\n          owner:\r\n            name: \"${resourceGroup.metadata.name}\"\r\n          location: \"${schema.spec.location}\"\r\n          environmentReference:\r\n            armId: \"${containerAppsEnv.status.id}\"\r\n          configuration:\r\n            ingress:\r\n              external: true\r\n              targetPort: ${schema.spec.targetPort}\r\n          template:\r\n            containers:\r\n              - name: app\r\n                image: \"${schema.spec.image}\"\r\n                resources:\r\n                  cpu: ${double(schema.spec.cpu)}\r\n                  memory: \"${schema.spec.memory}\"<\/pre>\n
As we can see, the “schema<\/em><\/strong>” section defines the structure (kind, fields and etc.<\/em>) of the custom resource we expose to developers. It is a kind of a contract between platform and the developers. It defines what developers can can configure. The “status<\/em><\/strong>” part in this section is simply outputs of this abstraction. It defines what information goes back to developers after deployment.<\/p>\n
The “resources<\/em><\/strong>” section is where we list the underlying ASO<\/em> resources that make up the abstraction. Each resource has an “id<\/em>” and a “template<\/em>” and KRO<\/em> analyzes the expressions inside these templates to understand how the resources relate to each other. So we don’t need to wire everything together ourself.<\/p>\n
For example, in the the “containerApp<\/em>” resource, we referenced the Managed Environment <\/em>using this “${containerAppsEnv.status.id}<\/em><\/strong>” expression. Similarly in the “containerAppsEnv<\/em>” resource, we referenced the Resource Group<\/em> using “${resourceGroup.metadata.name}<\/em><\/strong>” expression.<\/p>\n
From these references, KRO<\/em> builds a Directed Acyclic Graph<\/em> (DAG<\/em>) and compute the topological order. We will see this in action once we apply the definition. You can find all details about KRO’<\/em> graph inference here<\/a>\u00a0<\/em>and you can see all supported ASO<\/em> resources listed here<\/a><\/em>.<\/p>\n
Let’s apply this definition and get the “ACAStarterkit<\/em>” CRD <\/em>created.<\/p>\n
kubectl apply -f aca-starterkit.yaml\r\nkubectl get resourcegraphdefinition<\/pre>\n
\"\"<\/a><\/p>\n
Now let’s describe it to see the topological order that we mentioned.<\/p>\n
kubectl describe resourcegraphdefinition aca-starterkit<\/pre>\n
\"\"<\/a><\/p>\n
As we can see, KRO<\/em> built the dependency graph for our abstraction and figured out that the resource group must be created first, then the managed environment and then the container app.<\/p>\n
Let’s Deploy an Application Using the ACAStarterkit CRD<\/h2>\n
Since everything is in place, we can now start using this CRD<\/em> just like any other Kubernetes<\/em> resource. This is where the DevEx <\/em><\/strong>really begins, all the underlying complexity is hidden behind a single, simple interface.<\/p>\n
There are many ways to integrate this abstraction into the platform. For example, the platform team could expose this CRD<\/em> through Backstage<\/em> by adding it to the template catalog as a starter kit, or bundle it into any software boilerplates, golden templates so developers can have an end to end opinionated experience with just a few clicks and start experimenting. The key idea here remains the same, this CRD<\/em> becomes a reusable building block<\/strong> inside the IDP.<\/em><\/p>\n
Let\u2019s create our first “ACAStarterkit<\/em>” instance and watch KRO<\/em> orchestrate the underlying Azure<\/em> resources for us.<\/p>\n
For the sake of simplicity, I will skip Backstage<\/em>, scaffolding <\/em>and templating<\/em> workflows. We already covered those in detail in the earlier parts of this series. Instead, we will apply a minimal “ACAStarterkit<\/em>” resource directly to the cluster to provision the Azure<\/em> resources and deploy a simple \u201cquickstart<\/em>\u201d container image.<\/p>\n
apiVersion: kro.run\/v1alpha1\r\nkind: ACAStarterkit\r\nmetadata:\r\n  name: my-hello-world-app\r\n  namespace: default\r\nspec:\r\n  location: westeurope\r\n  image: mcr.microsoft.com\/k8se\/quickstart:latest\r\n  # cpu: \"0.5\" - optional\r\n  # memory: \"1Gi\" - optional\r\n  # targetPort: 80 - optional<\/pre>\n
kubectl apply -f hello-world.yaml<\/pre>\n
After applying this “ACAStarterkit<\/em>” resource, let’s monitor the deployment by describing it.<\/p>\n
kubectl describe acastarterkit my-hello-world-app<\/pre>\n
\"\"<\/a><\/p>\n
If we look at the “Status<\/em>” section, we can see the overall deployment state, the progress and once provisioning is completed, the output values that we exposed such as “App Fqdn<\/em>” and “Resource Group Name<\/em>“.<\/p>\n
If we want more detailed reconciliation progress of the underlying Azure<\/em> resources, for example if things are taking a bit longer, we can also inspect each resource type individually.<\/p>\n
NOTE<\/em><\/strong>: Depending on the Azure resource type, provisioning might take some time.<\/em><\/p><\/blockquote>\n
kubectl get resourcegroups,managedenvironments,containerapps<\/pre>\n
\"\"<\/a><\/p>\n
This also shows the status and error messages from ASO<\/em> as it provisions resources in Azure<\/em>. We can also see that the resources are created sequentially based on the dependency graph that KRO<\/em> inferred.<\/p>\n
Since all the resources got provisioned by our minimal platform cluster, we can now access the application through the exposed “App Fqdn<\/em>” output and verify that its running.<\/p>\n
\"\"<\/a><\/p>\n
As we can see, our quickstart container app running on ACA<\/em> and fully provisioned through the “ACAStarterkit<\/em>” abstraction in a simple and declarative way.<\/p>\n
Wrapping Up<\/h1>\n
In this article, I tried to show how KRO<\/em> and ASO<\/em> work together and lay the foundation for an Azure<\/em> focused platform setup. What we built here is the starting point of a lightweight, Azure<\/em> focused IDP<\/em>. Its minimal but solid and it gives us a clear and approachable path that can grow into a full IDP experience over time.<\/p>\n
From here, we can extend the abstraction and integrate GitOps<\/em>, OPA<\/em> and Backstage<\/em> to turn this platform foundation into a more complete developer portal and IDP<\/em> experience.<\/p>\n
References<\/h1>\n
https:\/\/azure.github.io\/azure-service-operator\/
\nhttps:\/\/kro.run\/docs\/getting-started\/Installation\/#installation
\nhttps:\/\/github.com\/Azure\/azure-service-operator\/blob\/main\/docs\/troubleshooting.md
\n<\/em><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"
In the first two parts of this DevEx series, I tried to show how golden paths in Backstage can enable developer self\u2011service without chaos and how extending the catalog into copilots with MCP servers transforms discoverability into a conversational experience. Both of these steps were…<\/p>\n
Devam\u0131n\u0131 okuyunDevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO<\/span><\/a><\/div>\n","protected":false},"author":1,"featured_media":4876,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[418,680,434],"tags":[729,728,731,717,716,719,721,720,727,440,730,718],"class_list":["post-4839","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","category-cloud","category-containerizing","tag-aks","tag-aso","tag-azure-service-operator","tag-developer-experience","tag-devex","tag-idp","tag-internal-developer-platform","tag-internal-developer-portal","tag-kro","tag-kubernetes","tag-kubernetes-resource-orchestrator","tag-platform-engineering","entry"],"translation":{"provider":"WPGlobus","version":"3.0.2","language":"tr","enabled_languages":["en","tr"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"tr":{"title":false,"content":false,"excerpt":false}}},"yoast_head":"\nDevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp\" \/>\n<meta property=\"og:url\" content=\"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/\" \/>\n<meta property=\"og:site_name\" content=\"G\u00f6khan G\u00f6kalp\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-06T19:51:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-06T19:56:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"675\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"G\u00f6khan G\u00f6kalp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"G\u00f6khan G\u00f6kalp\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/\"},\"author\":{\"name\":\"G\u00f6khan G\u00f6kalp\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#\\\/schema\\\/person\\\/7e2a7fa98babd22a5fdae563c4b8cdbe\"},\"headline\":\"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO\",\"datePublished\":\"2026-01-06T19:51:03+00:00\",\"dateModified\":\"2026-01-06T19:56:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/\"},\"wordCount\":1664,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#\\\/schema\\\/person\\\/7e2a7fa98babd22a5fdae563c4b8cdbe\"},\"image\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/gokhan-gokalp-idp-aso-kro.jpg\",\"keywords\":[\"aks\",\"aso\",\"azure service operator\",\"developer experience\",\"devex\",\"idp\",\"internal developer platform\",\"internal developer portal\",\"kro\",\"kubernetes\",\"kubernetes resource orchestrator\",\"platform engineering\"],\"articleSection\":[\"Azure\",\"Cloud\",\"Containerizing\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/\",\"url\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/\",\"name\":\"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/gokhan-gokalp-idp-aso-kro.jpg\",\"datePublished\":\"2026-01-06T19:51:03+00:00\",\"dateModified\":\"2026-01-06T19:56:40+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#primaryimage\",\"url\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/gokhan-gokalp-idp-aso-kro.jpg\",\"contentUrl\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/gokhan-gokalp-idp-aso-kro.jpg\",\"width\":1200,\"height\":675},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/gokhan-gokalp.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#website\",\"url\":\"https:\\\/\\\/gokhan-gokalp.com\\\/\",\"name\":\"G\u00f6khan G\u00f6kalp\",\"description\":\"C# & Python lover\",\"publisher\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#\\\/schema\\\/person\\\/7e2a7fa98babd22a5fdae563c4b8cdbe\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/gokhan-gokalp.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/#\\\/schema\\\/person\\\/7e2a7fa98babd22a5fdae563c4b8cdbe\",\"name\":\"G\u00f6khan G\u00f6kalp\",\"pronouns\":\"he\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/litespeed\\\/avatar\\\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659\",\"url\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/litespeed\\\/avatar\\\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659\",\"contentUrl\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/litespeed\\\/avatar\\\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659\",\"caption\":\"G\u00f6khan G\u00f6kalp\"},\"logo\":{\"@id\":\"https:\\\/\\\/gokhan-gokalp.com\\\/wp-content\\\/litespeed\\\/avatar\\\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659\"},\"sameAs\":[\"https:\\\/\\\/gokhan-gokalp.com\"],\"url\":\"https:\\\/\\\/gokhan-gokalp.com\\\/tr\\\/author\\\/gok-gokalp\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/","og_locale":"tr_TR","og_type":"article","og_title":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp","og_url":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/","og_site_name":"G\u00f6khan G\u00f6kalp","article_published_time":"2026-01-06T19:51:03+00:00","article_modified_time":"2026-01-06T19:56:40+00:00","og_image":[{"width":1200,"height":675,"url":"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg","type":"image\/jpeg"}],"author":"G\u00f6khan G\u00f6kalp","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"G\u00f6khan G\u00f6kalp","Tahmini okuma s\u00fcresi":"9 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#article","isPartOf":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/"},"author":{"name":"G\u00f6khan G\u00f6kalp","@id":"https:\/\/gokhan-gokalp.com\/#\/schema\/person\/7e2a7fa98babd22a5fdae563c4b8cdbe"},"headline":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO","datePublished":"2026-01-06T19:51:03+00:00","dateModified":"2026-01-06T19:56:40+00:00","mainEntityOfPage":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/"},"wordCount":1664,"commentCount":0,"publisher":{"@id":"https:\/\/gokhan-gokalp.com\/#\/schema\/person\/7e2a7fa98babd22a5fdae563c4b8cdbe"},"image":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#primaryimage"},"thumbnailUrl":"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg","keywords":["aks","aso","azure service operator","developer experience","devex","idp","internal developer platform","internal developer portal","kro","kubernetes","kubernetes resource orchestrator","platform engineering"],"articleSection":["Azure","Cloud","Containerizing"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/","url":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/","name":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO - G\u00f6khan G\u00f6kalp","isPartOf":{"@id":"https:\/\/gokhan-gokalp.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#primaryimage"},"image":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#primaryimage"},"thumbnailUrl":"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg","datePublished":"2026-01-06T19:51:03+00:00","dateModified":"2026-01-06T19:56:40+00:00","breadcrumb":{"@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/"]}]},{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#primaryimage","url":"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg","contentUrl":"https:\/\/gokhan-gokalp.com\/wp-content\/uploads\/2026\/01\/gokhan-gokalp-idp-aso-kro.jpg","width":1200,"height":675},{"@type":"BreadcrumbList","@id":"https:\/\/gokhan-gokalp.com\/devex-series-03-laying-the-azure-focused-platform-foundation-for-an-idp-with-aso-and-kro\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/gokhan-gokalp.com\/"},{"@type":"ListItem","position":2,"name":"DevEx Series 03: Laying the Azure Focused Platform Foundation for an IDP with ASO and KRO"}]},{"@type":"WebSite","@id":"https:\/\/gokhan-gokalp.com\/#website","url":"https:\/\/gokhan-gokalp.com\/","name":"G\u00f6khan G\u00f6kalp","description":"C# & Python lover","publisher":{"@id":"https:\/\/gokhan-gokalp.com\/#\/schema\/person\/7e2a7fa98babd22a5fdae563c4b8cdbe"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/gokhan-gokalp.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/gokhan-gokalp.com\/#\/schema\/person\/7e2a7fa98babd22a5fdae563c4b8cdbe","name":"G\u00f6khan G\u00f6kalp","pronouns":"he","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/gokhan-gokalp.com\/wp-content\/litespeed\/avatar\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659","url":"https:\/\/gokhan-gokalp.com\/wp-content\/litespeed\/avatar\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659","contentUrl":"https:\/\/gokhan-gokalp.com\/wp-content\/litespeed\/avatar\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659","caption":"G\u00f6khan G\u00f6kalp"},"logo":{"@id":"https:\/\/gokhan-gokalp.com\/wp-content\/litespeed\/avatar\/e645f66b6264ced10d7b6d8b1f85509b.jpg?ver=1776170659"},"sameAs":["https:\/\/gokhan-gokalp.com"],"url":"https:\/\/gokhan-gokalp.com\/tr\/author\/gok-gokalp\/"}]}},"_links":{"self":[{"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/posts\/4839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/comments?post=4839"}],"version-history":[{"count":29,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/posts\/4839\/revisions"}],"predecessor-version":[{"id":4875,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/posts\/4839\/revisions\/4875"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/media\/4876"}],"wp:attachment":[{"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/media?parent=4839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/categories?post=4839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gokhan-gokalp.com\/tr\/wp-json\/wp\/v2\/tags?post=4839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}