[SLO] HTTP2 support QA testing - SLO product

[jasonrhodes]

Summary

With the addition of HTTP2 support in Kibana, the Kibana platform team is asking us to run Kibana with HTTP2 support turned on and verify that our areas of the product do not display any obvious errors or problems.

Acceptance criteria

• Please run a local Kibana instance using the HTTP2 flag and test our SLO product, specifically:
  • Creating an SLO
  • Editing an SLO
  • Federated SLO flow
  • Auto-creation of the burn rate rule when creating an SLO
  • Deleting an SLO?
  • Anything else you can think of re: our SLO product and its interaction with HTTP calls from Kibana

Timebox: 2-3 hours, max

More details

From @pgayvallet's email:

HTTP2 is considered (and documented as) an experimental feature for now, and is disabled by default for obvious reasons.

In theory, having HTTP2 enabled should be an implementation detail for any feature that doesn't mess with things specific to HTTP/1.x (looking at you, bfetch), and our manual tests tend to confirm that.

The PR also adds integration tests and FTR smoke tests for the feature, however massively enabling HTTP2 for all FTR suites is a bit complicated (mostly due to the fact that we're using self-signed certificates, not really because of HTTP2 itself), so we can't be fully sure everything works as expected, given that, well, we did not ran all FTR suites.

Which is why we need you: if some of you could do just some surface / smoke tests of their Kibana apps, it would really be amazing and help us a lot.

HTTP2 can be enabled (for dev mode) simply by adding the --http2 flag when starting the server:

node scripts/kibana --dev --http2

If you prefer the long way, it can be done via the configuration file too

server.protocol: http2
server.ssl.enabled: true
server.ssl.certificate: {path-to-kibana}/packages/kbn-dev-utils/certs/kibana.crt
server.ssl.key: {path-to-kibana}/packages/kbn-dev-utils/certs/kibana.key

Please remember that enabling HTTP2 (one way or the other) enables HTTPS/TLS too. So to access your local instance, you need to use https instead of http, e.g. https://localhost:5601/base-path. (and also you need to discard the scary warning about self-signed certificates)

If you see anything that doesn't behave as expected when HTTP2 is enabled, or if you have any questions, please reach out to us on the #kibana-core channel.

Thanks a lot for your support

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[dominiqueclarke]

Also checked filtering, sorting, and groups. Everything LGTM

[jasonrhodes]

Thank you so much, @dominiqueclarke !