I would like to have multiple Graylog deployments installed in the same namespace. The first deployment correctly sets the master and coordinating graylog-role to the pods but in the next deployments it do create pods but they all come up with the coordinating role and for that deployment there is no master.
I checked and i found that in entrypoint.sh (which does the role selection and label creation) the logic uses the selector lable Release.Namespace
In helpers.tpl i see that we can use Release.Name also as the selector label
So, I believe the problem i mentioned can be solved by using Release.Name selector lable together with namespace and not just by namespace.
The working example which i tried and which finds the running master in my particular release is this:
kubectl get pod --namespace {{ .Release.Namespace }} -l app.kubernetes.io/instance={{ .Release.Name }} -l graylog-role=master --field-selector=status.phase=Running
Can you please help me with this?
I would like to have multiple Graylog deployments installed in the same namespace. The first deployment correctly sets the master and coordinating graylog-role to the pods but in the next deployments it do create pods but they all come up with the coordinating role and for that deployment there is no master.
I checked and i found that in entrypoint.sh (which does the role selection and label creation) the logic uses the selector lable Release.Namespace
In helpers.tpl i see that we can use Release.Name also as the selector label
So, I believe the problem i mentioned can be solved by using Release.Name selector lable together with namespace and not just by namespace.
The working example which i tried and which finds the running master in my particular release is this:
kubectl get pod --namespace {{ .Release.Namespace }} -l app.kubernetes.io/instance={{ .Release.Name }} -l graylog-role=master --field-selector=status.phase=Running
Can you please help me with this?