CRD for CRDs to design multi-tenant platform services from Helm charts

  • Compose new CRDs (Custom Resource Definitions) to publish platform services from Helm charts
  • Define policies (e.g. Node selection, CPU/Memory limits, etc.) for managing resources of the platform services
  • Get aggregated CPU/Memory/Storage Prometheus metrics for the platform services
  • Create a PersistentVolume of required type for MySQL instance.
  • Create Secret objects for MySQL instance and AWS backup.
  • Create a MySQL instance with a backup target as AWS S3 bucket.
  • Setup a policy in such a way that Pods created under this service will have specified Resource Request and Limits.
  • Get aggregated CPU/Memory metrics for the overall workflow.




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

Recommended from Medium

Integrating with Azure AD SAML 2.0 SSO using Devise Token Auth and Ember Simple Auth (Part 2)

sp config

How critical are your systems?

Deploying a Smart Contract using Tezster Bundles and Local Nodes using Tezsure CLI

Automating Web Application Deployment on Kubernetes using Groovy

All Things Clock, Time and Order in Distributed Systems: Logical Clocks in Real Life (2)

9 clusters to make the best use case choices for 5G

Aws RDS : Production — High availability — Security — Cost effective

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

HashiCorp Nomad

Newsletter of Carlos Santana — Issue #30

ELK vs Prometheus/Grafana/Jaeger

Installing istio service mesh using istioctl