When it comes to deploying JFrog products in Kubernetes, it is always a best practice to keep everything updated and managed through our Helm chart.
In advanced cases where you would like to have extra Kubernetes resources that our Chart doesn't deploy by default, you may use the additionalResources key, to build your own Kubernetes resources, that can utilize the chart’s values and template.
You may add as many resources as you would like, but keep in mind that they must be separated with a ---, with each new line.
Here is an example of deploying an additional resource (ServiceMonitor used for Prometheus) in Artifactory’s chart, while also using some of the chart's values and variables for demonstrating purposes:
artifactory:
replicaCount: 1
additionalResources: |
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
name: servicemonitor-{{ template "artifactory.name" . }}
labels:
metrics: jfrog
app: {{ template "artifactory.name" . }}
chart: {{ template "artifactory.chart" . }}
heritage: {{ .Release.Service }}
release: prometheus
spec:
selector:
matchLabels:
app: {{ template "artifactory.name" . }}
component: {{ template "artifactory.name" . }}
endpoints:
- port: metrics
interval: 15s
This way, you can manage and update your additional Kubernetes resources through our chart.
NOTE: This is supported across all of our charts.