fix

charts/rabbitmq/Chart.yaml

@@ -15,11 +15,11 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.0.1
+version: 1.0.2
 
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "2.2.1"
+appVersion: "2.2.2"

charts/rabbitmq/templates/servicemonitor.yaml

@@ -3,6 +3,8 @@ kind: ServiceMonitor
 metadata:
   name: rabbitmq-service-monitor
   namespace: {{ .Release.Namespace }}
+  labels:
+    app.kubernetes.io/vendor: kubesphere
   # If labels are defined in spec.serviceMonitorSelector.matchLabels of your deployed Prometheus object, make sure to include them here.
 spec:
   endpoints:

charts/rabbitmq/values.yaml

@@ -10,7 +10,7 @@ manager:
       memory: 500Mi
   image: rabbitmq-operator
   ## tag default uses appVersion from Chart.yaml, to override specify tag tag: "v1.1"
-  tag: "2.2.1"
+  tag: "2.2.2"
   # If a watchNamespace is specified, the manager's cache will be restricted to
   # watch objects in the desired namespace. Defaults is to watch all namespaces.
   watchNamespace: