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

How to sort a list of dictionaries by values in Python?

Getting Lost in Unsafe Region

Go Lang echo & gorm v/s Laravel performance results.

Being in a sexless relationship in my twenties destroyed me as a person

Postman API Test

Pillars of Object Oriented Programming (in Python)

What is Amazon S3?

Why Software Sucks: Matilda and Hansel

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

Deploying Argo CD and Sealed Secrets with Helm

Canary Deployment in Kubernetes (Part 3) — Smart Canary Deployment using Argo Rollouts and…

Automation Workflows: GitOps for YugabyteDB with Argo CD and Helm

How to tackle Kubernetes observability challenges with Pixie