--- title: Building tools to manage cross-cutting concerns in... description: A suite of Kubernetes workload management tools built on ConfigHub demonstrates the 'configuration as data' approach to handling cross-cutting concerns. Four... canonical: https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Building tools to manage cross-cutting concerns in Kubernetes | daily.dev og:description: A suite of Kubernetes workload management tools built on ConfigHub demonstrates the 'configuration as data' approach to handling cross-cutting concerns. Four... og:url: https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn og:image: https://api.daily.dev/og/posts/ksY5gQSpn.png og:image:alt: Building tools to manage cross-cutting concerns in Kubernetes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Building tools to manage cross-cutting concerns in Kubernetes **[ITNEXT](https://daily.dev/sources/itnext)** · 8 min read · 1 upvotes · 0 comments ## Summary A suite of Kubernetes workload management tools built on ConfigHub demonstrates the 'configuration as data' approach to handling cross-cutting concerns. Four tools are introduced: workload-manager (best practices enforcement), scheduling-manager (node selectors/affinity/tolerations), observability-manager (Prometheus ServiceMonitor and OpenTelemetry sidecar), and autoscale-manager (HPA/KEDA). Unlike configuration-as-code approaches requiring template edits and re-rendering, these tools operate directly on materialized configuration stored in a database, enabling composable and interoperable automation. Tools run in dry-run mode by default for agent-friendliness, support guardrails via triggers, and can analyze, generate, validate, and enforce desired postures across multiple clusters without cloning git repos or creating PRs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the difference between configuration as code and configuration as data in Kubernetes tooling? Configuration as data stores fully materialized Kubernetes configuration in a database so tools can read and mutate it directly via APIs, while configuration as code requires cloning repos, rendering templates (helm, cdk8s, tanka), running policy checks, committing fixes, and re-rendering for every affected environment. ConfigHub uses the data model, letting tools like workload-manager or autoscale-manager change configuration directly without repo cloning or pull requests. _Developers weighing config-as-code versus config-as-data workflows can find deeper Kubernetes tooling discussion on daily.dev._ ### How do I create a PodDisruptionBudget for a Kubernetes workload without writing YAML by hand? A tool like cub-workload can generate one automatically: running 'ensure-pdb appchat-prod/frontend --max-unavailable "10%"' produces a dry-run PodDisruptionBudget matching the workload's namespace and labels, similar to how kubectl expose infers settings, making it simpler than kubectl create pdb. The change is only committed and applied to clusters after explicit approval. _Anyone automating PDBs and other Kubernetes hardening steps can track more workflow patterns like this on daily.dev._ ### Should I use HPA or KEDA for Kubernetes autoscaling? Both are viable, and tooling exists to convert between them: the autoscale-manager tool checks and edits HorizontalPodAutoscaler and KEDA ScaledObject resources and can convert an existing HPA configuration to KEDA. The choice often depends on whether autoscaling needs to react to external event sources, which KEDA supports beyond HPA's built-in metrics. _Teams deciding between HPA and KEDA for scaling policy can follow related Kubernetes autoscaling coverage on daily.dev._ ## Similar posts on daily.dev - [There should be an app for that](https://daily.dev/posts/there-should-be-an-app-for-that-uiole5bw7) · ITNEXT · 5 upvotes · 1 comments - [Building imperative operational tools on a declarative platform](https://daily.dev/posts/building-imperative-operational-tools-on-a-declarative-platform-8oc1jshpl) · ITNEXT · 0 upvotes · 1 comments - [The Karpenter Ecosystem: Which Tools Extend Karpenter, and What Each Adds](https://daily.dev/posts/the-karpenter-ecosystem-which-tools-extend-karpenter-and-what-each-adds-tnbnl2bxz) · Cast AI · 0 upvotes · 0 comments - [Tech Veterans’ New Approach To Eliminate ‘Configuration Hell’](https://daily.dev/posts/tech-veterans-new-approach-to-eliminate-configuration-hell--0j6xxahuq) · The New Stack · 1 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#iac](https://daily.dev/tags/iac) [View this post on daily.dev](https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Building tools to manage cross-cutting concerns in Kubernetes","url":"https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn"},"datePublished":"2026-07-13T17:35:51.438Z","dateModified":"2026-09-14T08:02:09.510Z","description":"A suite of Kubernetes workload management tools built on ConfigHub demonstrates the 'configuration as data' approach to handling cross-cutting concerns. Four...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9ccc328958f38675d9d1f816797964ba?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9ccc328958f38675d9d1f816797964ba?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ITNEXT","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ITNEXT","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/itnext2","url":"https://daily.dev/sources/itnext"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,iac","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ITNEXT","item":"https://daily.dev/sources/itnext"},{"@type":"ListItem","position":3,"name":"Building tools to manage cross-cutting concerns in Kubernetes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-tools-to-manage-cross-cutting-concerns-in-kubernetes-ksy5gqspn#faq","mainEntity":[{"@type":"Question","name":"What is the difference between configuration as code and configuration as data in Kubernetes tooling?","acceptedAnswer":{"@type":"Answer","text":"Configuration as data stores fully materialized Kubernetes configuration in a database so tools can read and mutate it directly via APIs, while configuration as code requires cloning repos, rendering templates (helm, cdk8s, tanka), running policy checks, committing fixes, and re-rendering for every affected environment. ConfigHub uses the data model, letting tools like workload-manager or autoscale-manager change configuration directly without repo cloning or pull requests. Developers weighing config-as-code versus config-as-data workflows can find deeper Kubernetes tooling discussion on daily.dev."}},{"@type":"Question","name":"How do I create a PodDisruptionBudget for a Kubernetes workload without writing YAML by hand?","acceptedAnswer":{"@type":"Answer","text":"A tool like cub-workload can generate one automatically: running 'ensure-pdb appchat-prod/frontend --max-unavailable \"10%\"' produces a dry-run PodDisruptionBudget matching the workload's namespace and labels, similar to how kubectl expose infers settings, making it simpler than kubectl create pdb. The change is only committed and applied to clusters after explicit approval. Anyone automating PDBs and other Kubernetes hardening steps can track more workflow patterns like this on daily.dev."}},{"@type":"Question","name":"Should I use HPA or KEDA for Kubernetes autoscaling?","acceptedAnswer":{"@type":"Answer","text":"Both are viable, and tooling exists to convert between them: the autoscale-manager tool checks and edits HorizontalPodAutoscaler and KEDA ScaledObject resources and can convert an existing HPA configuration to KEDA. The choice often depends on whether autoscaling needs to react to external event sources, which KEDA supports beyond HPA's built-in metrics. Teams deciding between HPA and KEDA for scaling policy can follow related Kubernetes autoscaling coverage on daily.dev."}}]} ```