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

Productize ElasticSearch deployment #29

Closed
NicolasT opened this issue Mar 23, 2018 · 0 comments
Closed

Productize ElasticSearch deployment #29

NicolasT opened this issue Mar 23, 2018 · 0 comments
Labels
kind:bug Something isn't working kind:enhancement New feature or request topic:operations Operations-related issues

Comments

@NicolasT
Copy link
Contributor

NicolasT commented Mar 23, 2018

The current ElasticSearch deployment is not production-ready:

  • It's not using stateful storage / deployed as a StatefulSet
  • JVM memory settings are low
  • Only one CPU assigned to services
  • No PodDistuptionBudgets deployed
  • Curator config is very basic
  • Fluentd config is very basic

Some of these are already handled by the vendored deployment files, other things need to be manually changed.

See #27

@NicolasT NicolasT added kind:bug Something isn't working kind:enhancement New feature or request topic:operations Operations-related issues labels Mar 23, 2018
NicolasT added a commit that referenced this issue May 23, 2018
NicolasT added a commit that referenced this issue May 23, 2018
@NicolasT NicolasT self-assigned this May 29, 2018
@NicolasT NicolasT added this to the MetalK8s 1.0.0 milestone Jun 29, 2018
@NicolasT NicolasT removed their assignment Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug Something isn't working kind:enhancement New feature or request topic:operations Operations-related issues
Projects
None yet
Development

No branches or pull requests

1 participant