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

Functional Test Server - HA deployment of Kibana #79743

Open
kobelb opened this issue Oct 6, 2020 · 1 comment
Open

Functional Test Server - HA deployment of Kibana #79743

kobelb opened this issue Oct 6, 2020 · 1 comment
Labels
enhancement New value added to drive a business result impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Operations Team label for Operations Team

Comments

@kobelb
Copy link
Contributor

kobelb commented Oct 6, 2020

It's incredibly common for us to recommend that users deploy multiple instances of Kibana behind a load-balancer. This allows users to get more throughput out of Kibana, and not experience downtime if a single instance crashes. As such, it's important that we're confident that Kibana behaves properly in this configuration.

Currently, the functional test server runs a single instance of Kibana that isn't behind a load balancer. It'd be incredibly helpful to be able to run all functional tests against a HA deployment of Kibana run by the functional test server.

There are currently some Cloud tests that run against a HA deployment of Kibana; however, these tests are run very infrequently and are a subset of the total functional test.

@kobelb kobelb added Team:Operations Team label for Operations Team enhancement New value added to drive a business result labels Oct 6, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@tylersmalley tylersmalley added 1 and removed 1 labels Oct 11, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Feb 16, 2022
@tylersmalley tylersmalley removed loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. EnableJiraSync labels Mar 16, 2022
@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

3 participants