|
4 months ago | |
---|---|---|
README.md | 4 months ago | |
deploy.yaml | 4 months ago | |
graylog.conf | 4 months ago | |
log4j2.xml | 4 months ago | |
namespace.yaml | 4 months ago | |
node-id | 4 months ago | |
pvc.yaml | 4 months ago |
Due to behaviour of graylog a little bit of shenanigans are required to make it work in the single pod - single pvc pattern.
kubectl apply -f namespace.yaml
kubectl apply -f pvc.yaml
kubectl exec -it -n graylog prepper -- sh
Next you want to want to run in the container
# the graylog user
chown -R 1100:1100 /vol
# delete lost and found
cd vol
rm -r *
Next you want to echo all 3 files (graylog.conf, log4j2.xml, and node-id) into that directory. These are needed to make graylogs configuration (inputs and so on, persistent).
Exit and remove the preparation pod
exit
kubectl delete pod -n graylog prepper
Set the environment variable GRAYLOG_HTTP_EXTERNAL_URI
of the graylog deployment to the url it will acutally be accessible at. It doesn’t matter if it’s http or https.
Graylog simply uses it to construct dynamic links, since it somehow doesn’t look for it’s own hostname.
kubectl apply -f deploy.yaml