Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fluentd persistence of logs in Elasticsearch and of config of Kibana #53

Open
stygmate opened this issue May 27, 2022 · 3 comments
Open

Comments

@stygmate
Copy link

Summary

adding parameters to enable script to define persistence parameters for ES and Kibana data.

Why is this important?

loosing all logs in case of rescheduling is not ok in production.

Are you interested in contributing to this feature?

maybe, if i have time.

Question:

What is the best way to configure persistent storage for now ?

@madalinignisca
Copy link

ELK will use default storage class. This is not the responsibility of the ELK addon. Any Kubernetes administrator would setup storage and define a default class before anything else; I assume that who originally created the addon made this assumption.

@stygmate
Copy link
Author

stygmate commented Jun 3, 2022

ELK will use default storage class. This is not the responsibility of the ELK addon. Any Kubernetes administrator would setup storage and define a default class before anything else; I assume that who originally created the addon made this assumption.

the creator of the addon use emptydir instead of pvc so default storage driver don't have anything to do with this. https://github.com/canonical/microk8s-community-addons/blob/main/addons/fluentd/fluentd/es-statefulset.yaml#L115

@madalinignisca
Copy link

@stygmate, auch, my bad, did not even looked over it, as I have my own setup for ELK. You are right. My first question that hit me was "WHYYY?".

I now think that addons must follow some conventions. Example, addons should support out of the box default storage class, or allow by some params to use a user given class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants