-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
R&D Capture metrics for Helm Charts and Repos
-
False
-
False
-
To Do
-
RHDP-286 - Drive metrics needs to allow us to properly target our workload and developer-focused adoption efforts
-
18% To Do, 0% In Progress, 82% Done
-
Undefined
Goal:
Product and Engineering teams require greater insight into how Helm charts are deployed in order to make informed product and resourcing decisions in order to deliver what customers need, thus driving workloads to the platform.
Would like to capture:
- How many Helm charts are in use
- How many clusters use Helm charts
- Which Helm charts are installed
- Which installation method was used (e.g. UI vs cli)
Metrics to capture:
Initial Scope (easiest to capture):
- Usage of Helm Chart
- Installation:
- Identify the list of the Charts that are installed
- For each chart, we would like to know:
- Name
- Version
- Repository
- We should group the result by chart name and version
- Deployment
- How many chart releases are running
- For each chart releases
- Name
- Version
- Repository
- We should group the result by chart name and version
- Installation:
Scope #2:
- Usage of custom Helm Chart Repository
- We would like to capture the name/url of the repository and how many "users" are using it
Further Scope:
- Identifying the tool that was used to do the installation of the Chart
Problem:
Helm product development lacks adequate insight into how helm charts are being used and deployed.
Why is this important:
See Goal section.