-
-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Describe the bug a clear and concise description of what the bug is.
I found an issue when deploying chart version 2.0.0 and upwards.
The label "opencti.component" is being declared in two places, which results in being applied twice. Which is causing the deployment to fail.
First declaration:
| opencti.component: {{ $serverType }} |
Second declaration:
| opencti.component: server |
This templating results in this:
# Source: opencti/templates/server/service.yaml
apiVersion: v1
kind: Service
metadata:
name: opencti-server
labels:
app.kubernetes.io/instance: opencti
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: opencti
app.kubernetes.io/version: 6.8.3
helm.sh/chart: opencti-2.0.10
opencti.component: server
opencti.component: server
spec:
type: ClusterIP
ports:
- port: 80
targetPort: 4000
protocol: TCP
name: http
appProtocol: HTTP
- name: metrics
port: 14269
targetPort: 14269
protocol: TCP
selector:
app.kubernetes.io/instance: opencti
app.kubernetes.io/name: opencti
opencti.component: server
opencti.component: serverWhat's your helm version?
version.BuildInfo{Version:"v3.18.6", GitCommit:"b76a950f6835474e0906b96c9ec68a2eff3a6430", GitTreeState:"clean", GoVersion:"go1.25.0"}
What's your kubectl version?
Client Version: v1.34.1 Kustomize Version: v5.7.1 Server Version: v1.33.1
Chart version
2.0.0+
Explain bug
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute when chart failing/misfunctioning
helm template opencti opencti/opencti --values apps/opencti/values.yaml
More info
The chart is being deployed by FluxCD:
flux: v2.6.4
distribution: flux-v2.6.4
helm-controller: v1.3.0
image-automation-controller: v0.41.2
image-reflector-controller: v0.35.2
kustomize-controller: v1.6.1
notification-controller: v1.6.0
source-controller: v1.6.2