Closed uwe-mayer closed 2 months ago
This can be done by providing a custom ConfigMap with the Greenhouse Chart, which is then passed to the logshipper
plugin.
Current default ConfigMap:
https://github.com/cloudoperators/greenhouse-extensions/blob/main/logshipper/chart/templates/fluent-bit-configmap.yaml
The used ConfigMap needs to be deployed to the same namespace as fluent-bit, and the name specified here:
https://github.com/cloudoperators/greenhouse-extensions/blob/main/logshipper/chart/values.yaml#L9
When doing this the templating of the default ConfigMap should be made optional.
Implemented in https://github.com/cloudoperators/greenhouse-extensions/pull/375 and #528
Message is not yet parsed, as I need some advice from @Kuckkuck once he is back next week.
Priority
(Medium) I'm annoyed but I'll live
Description
We need the possibility to forward Greenhouse Controller logs to an ElasticSearch endpoint for scenarios where we cannot audit log the k8s apiserver (e.g. Greenhouse running on managed k8s cluster)
Reference Issues
https://github.com/cloudoperators/greenhouse/issues/388