-
Feature
-
Resolution: Obsolete
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
For this feature request, my customer would like to automate detecting what subscription is used by workloads on their clusters, at pod and namespace levels, to tag them so that the cost management solution can be used along this. They need a base that would be provided by Red Hat for the purpose to identify what is used by what and methods to identify what their end customer is using and running on the OCP they provide.
My customer is working to provide OCP environments to their end customer and wants to automatically tag workloads in OCP that would be identified as using what is provided by one of the Red Hat subscriptions amongst the following sample
| sku | name |
|---|---|
| MW00005 | Red Hat AMQ for Openshift Container Platform, Standard (2 cores or 4 vCPUs) |
| MW00006 | Red Hat AMQ for Openshift Container Platform, Premium (2 cores or 4 vCPUs) |
| MW00001 | Red Hat Fuse for Openshift Container Platform, Standard (2 cores or 4 vCPUs) |
| MW00002 | Red Hat Fuse for Openshift Container Platform, Premium (2 cores or 4 vCPUs) |
| MW02006 | Red Hat Application Foundations, Standard (2 Cores or 4 vCPUs) |
| MW02000 | Red Hat Application Foundations, Premium (2 Cores or 4 vCPUs) |
| MW00280 | Red Hat Runtimes, Standard (2 Cores or 4 vCPUs) |
| MW00277 | Red Hat Runtimes, Premium (2 Cores or 4 vCPUs) |
Putting aside the differences of Premium and Standard, a lot of the subscriptions share the same common channel access and are hard to identify on their own within possibly intrusive access level to the workloads.
The tags would then be used with the cost management solution to track usage and costs with an emphasis on usage, aiming to identify the value taken from the subscription per cluster and identifying what it uses.
