Provider and Consumer personas co-operating on Kubernetes

  • Consumer API that allows them to expose only minimum set of parameters that they want consumers to control
  • Ability to troubleshoot and monitor the application instance
  • Ability to track consumption of the software by different consumers
  • API-based access to Helm charts on a cluster.
  • Seamless support for Namespace-based multi-tenancy where each application instance (Helm release) can be deployed in a separate namespace.
  • Monitoring of application instances.
  • Tracking consumption metrics (cpu, memory, storage and network) at Helm release / application instance level. (Providers can use these metrics to define consumption-based chargeback model).




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Handy MySQL Date functions with examples.

Azure Subscriptions

Substack Repost — OpenLampTech issue #20

SCP: Labrat Devlog #1

ClickHelp July 2020 Release Overview — Gecko

Sql Language

InsureDAO updates & what’s upcoming in Q2

Import Export CSV/EXCEL File In Laravel

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


More from Medium

Kubernetes RBAC — Update default ClusterRoles without editing them

Container Security Asset Management

[Prometheus] What is the difference between rate and irate

Integrate Open policy agent(OPA) with Terraform to restrict S3 bucket creation with versioning…