Could someone please explain cleanness of "Rancher...
# general
l
Could someone please explain cleanness of "Rancher Prime" subscription/paywall to me ? I know that images are "hardened" (for example, the base image is some sort of a minimized SLE Linux userspace). For example, if I compare for example https://apps.rancher.io/applications/alertmanager with https://artifacthub.io/packages/helm/prometheus-community/alertmanager the charts have changed minimally, but the LICENSE and original authors/maintainers have been removed (due to the takeover script patches/Chart.yaml.tpl)
Copy code
$ diff -r -u original/ suse/
diff -r -u original/alertmanager/Chart.yaml suse/alertmanager/Chart.yaml
--- original/alertmanager/Chart.yaml	2025-09-03 18:23:29.000000000 +0200
+++ suse/alertmanager/Chart.yaml	2025-09-03 18:38:14.000000000 +0200
@@ -1,26 +1,20 @@
 annotations:
-  <http://artifacthub.io/license|artifacthub.io/license>: Apache-2.0
-  <http://artifacthub.io/links|artifacthub.io/links>: |
-    - name: Chart Source
-      url: <https://github.com/prometheus-community/helm-charts>
+  <http://helm.sh/images|helm.sh/images>: |
+    - image: <http://dp.apps.rancher.io/containers/alertmanager:0.28.1-10.9|dp.apps.rancher.io/containers/alertmanager:0.28.1-10.9>
+      name: alertmanager
+    - image: <http://dp.apps.rancher.io/containers/prometheus-config-reloader:0.85.0-9.9|dp.apps.rancher.io/containers/prometheus-config-reloader:0.85.0-9.9>
+      name: prometheus-config-reloader
 apiVersion: v2
-appVersion: v0.28.1
+appVersion: 0.28.1
 description: The Alertmanager handles alerts sent by client applications such as the
-  Prometheus server.
-home: <https://prometheus.io/>
-icon: <https://raw.githubusercontent.com/prometheus/prometheus.github.io/master/assets/prometheus_logo-cb55bb5c346.png>
-keywords:
-- monitoring
-kubeVersion: '>=1.25.0-0'
+  Prometheus server. It takes care of deduplicating, grouping, and routing them to
+  the correct receiver integrations such as email, PagerDuty, OpsGenie, or many other
+  mechanisms thanks to the webhook receiver. It also takes care of silencing and inhibition
+  of alerts.
+home: <https://apps.rancher.io/applications/alertmanager>
+icon: <https://apps.rancher.io/logos/alertmanager.png>
 maintainers:
-- email: <mailto:monotek23@gmail.com|monotek23@gmail.com>
-  name: monotek
-  url: <https://github.com/monotek>
-- email: <mailto:naseem@transit.app|naseem@transit.app>
-  name: naseemkullah
-  url: <https://github.com/naseemkullah>
+- name: SUSE LLC
+  url: <https://www.suse.com/>
 name: alertmanager
-sources:
-- <https://github.com/prometheus/alertmanager>
-type: application
 version: 1.26.0
...
c
Let me take a deeper look at this please DM me if you have any questions.
m
Thanks @clever-analyst-23771 for having brought that topic to our team. We have made improvements regarding our chart licenses and their related metadata. You will now be able to easily check a chart’s annotations and verify which license is the chart’s source code under. At the same time, we have standardized every relevant
LICENSE
and
NOTICE
file.
Copy code
$ helm show chart <oci://dp.apps.rancher.io/charts/alertmanager> | yq '.annotations.license'
...
Apache-2.0
We also plan to document this licence-related information. We will keep you posted.
👍 1