Siri

The TCP and UDP are running on different k8s services. Did you send to correct service name? Or it may depends on cloud provider. Some annotations may need.

What is your PVC access mode? It should be `ReadWriteOnce` or `ReadWriteMany` And make sure that `nfs-subdir-external-provisioner` has permission to write into the folder.

If you are using let's encrypt, yes that is correct. The chart does not support cert-manager. It is requires creating Certificate type.

@jpuskar thanks for reporting and patch. Can you make a PR? So we will have your name in the contributor list.

I'm agree that this method is not perfectly optimize since the Graylog itself does not have a mechanism to elect a new master by itself. You have to manual choose...

You can set `graylog.podSecurityContext` to `{}` when upgrading. It will override the new default value.

yes, you can propose a new image with better `wget` than `busybox` and submit a PR. There is no particular reason to use `busybox`. It is just every small image....

First, you need to put the truststore file here [graylog.serverFiles](https://github.com/KongZ/charts/blob/main/charts/graylog/values.yaml#L495) All file here will be mounted to `/etc/graylog/server` Second, add the `-Djavax.net.ssl.keyStore=/etc/graylog/server/keystore.jks` here [graylog.javaOpts](https://github.com/KongZ/charts/blob/main/charts/graylog/values.yaml#L63)

The `kubectl` is using for setting the label to master node. The chart uses label mechanism to choose the master node.

The solution described in the doc above will hard-code pod-0 to be the master. The solution in this chart will automatically set the other pod to be the master if...