About the service
I will write reusable libraries in Jsonnet and configuration for Kubernetes and Grafana that will transform overgrown, manually copied YAML into a compact and maintainable codebase. Jsonnet is a data templating language: it generates JSON and YAML from functions, variables and inheritance, so one change propagates across all environments instead of being fixed by hand in twenty files.
What's included in the work:
— Reusable libraries: parameterized functions, mixins and objects describing your services, so a new environment takes just a few lines instead of copying a directory.
— Kubernetes manifests: Deployment, Service, ConfigMap, Ingress and HPA, assembled for each environment (dev/stage/prod) from a single source of truth, ready for kubectl apply or Argo CD.
— Grafana dashboards: dashboards and panels as code via grafonnet, versioned and reviewed, without manual clicking in the interface.
— CI pipelines: build descriptions for your runner with common stages extracted.
— Tools: jsonnetfmt, jsonnet-lint and jsonnet-bundler, plus a render script in CI that checks the output on every commit.
I strictly follow the DRY principle: no duplicates, clear defaults, documented entry points. You get the source code, generated output, a short README and a walkthrough so your team can confidently develop the solution further. Send me your current config structure and target platform — I'll propose a schema.
What's included in the work:
— Reusable libraries: parameterized functions, mixins and objects describing your services, so a new environment takes just a few lines instead of copying a directory.
— Kubernetes manifests: Deployment, Service, ConfigMap, Ingress and HPA, assembled for each environment (dev/stage/prod) from a single source of truth, ready for kubectl apply or Argo CD.
— Grafana dashboards: dashboards and panels as code via grafonnet, versioned and reviewed, without manual clicking in the interface.
— CI pipelines: build descriptions for your runner with common stages extracted.
— Tools: jsonnetfmt, jsonnet-lint and jsonnet-bundler, plus a render script in CI that checks the output on every commit.
I strictly follow the DRY principle: no duplicates, clear defaults, documented entry points. You get the source code, generated output, a short README and a walkthrough so your team can confidently develop the solution further. Send me your current config structure and target platform — I'll propose a schema.
