-
-
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.
When I upgraded opencti from chart 2.0.9 to chart 2.0.19 I lost access to the web service. Then I noticed that the kubernetes services for these 2 deployments don't have any target.
The cluster has 2 main components: frontend and ingestion. This information is added to their deployments as a label: opencti.component: frontend and opencti.component: ingestion respectively.
The service selector for both frontend and ingestion have the label opencti.component: server which is not included in any pod and therefore they don't have any target.
I believe commit 1039cdc broke the services selector when clustering is enabled.
What's your helm version?
version.BuildInfo{Version:"v3.18.3", GitCommit:"6838ebcf265a3842d1433956e8a622e3290cf324", GitTreeState:"clean", GoVersion:"go1.24.4"}
What's your kubectl version?
Client Version: v1.30.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.30.1
Chart version
v2.0.19
Explain bug
No response
What you expected to happen?
When I describe the frontend and ingestion services, they should have some endpoints:
kubectl -n opencti describe svc opencti-frontend
Name: opencti-frontend
Namespace: opencti
Labels: app.kubernetes.io/instance=opencti
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=opencti
app.kubernetes.io/version=6.8.8
helm.sh/chart=opencti-1.0.0
opencti.component=frontend
Annotations: argocd.argoproj.io/tracking-id: opencti:/Service:opencti/opencti-frontend
Selector: app.kubernetes.io/instance=opencti,app.kubernetes.io/name=opencti,opencti.component=frontend
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 888.888.888.888
IPs: 888.888.888.888
Port: http 80/TCP
TargetPort: 4000/TCP
Endpoints: 10.1.1.11:4000,10.1.1.10:4000
Session Affinity: None
Events: <none>
How to reproduce it?
Cannot access opencti web service
kubectl -n opencti describe svc opencti-frontend
Name: opencti-frontend
Namespace: opencti
Labels: app.kubernetes.io/instance=opencti
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=opencti
app.kubernetes.io/version=6.8.8
helm.sh/chart=opencti-1.0.0
opencti.component=frontend
Annotations: argocd.argoproj.io/tracking-id: opencti:/Service:opencti/opencti-frontend
Selector: app.kubernetes.io/instance=opencti,app.kubernetes.io/name=opencti,opencti.component=server
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 888.888.888.888
IPs: 888.888.888.888
Port: http 80/TCP
TargetPort: 4000/TCP
Endpoints: <none>
Session Affinity: None
Events: <none>
Enter the changed values of values.yaml?
No response
Enter the command that you execute when chart failing/misfunctioning
To fix the the problem, i modified the frontend and ingestion services
kubectl -n opencti edit svc opencti-frontend
kubectl -n opencti edit svc opencti-ingestion
to add to the selector opencti.component: frontend and opencti.component: ingestion respectively
More info
No response