-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Document reporting network policy #71484
Comments
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Hi @legrego I think we should get started on this in the upcoming weeks. Any advice on starters for this documentation? Do you know of other places it exists in the docs that we can copy from or link to? Thanks! |
@tsullivan The closest I found is what Elasticsearch documents for connection filtering: https://www.elastic.co/guide/en/elasticsearch/reference/current/ip-filtering.html. There's nothing else in Kibana like this, so we get to be pioneers here 😄. I think starting with a summary of what this is intended to do would be a good start, followed by the available configuration options, followed by a simple example & a complex example. I'd like to get @gchaps's opinion on this, but it might be worthwhile to include a link to these new docs in the "Use Kibana in a production environment" section too. |
@legrego Nice explanation of what to include in the docs, especially the examples. I do think it would be worthwhile to link to the new docs in Use Kibana in a production environment. @tsullivan Happy to help with a review of the docs. |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Hi team, I took a crack at this issue today, and posted this PR for your review: #80431 |
The options for configuring Reporting's network policy are not documented currently. Having docs explaining how and why to use this would help users further secure their Kibana installations.
The text was updated successfully, but these errors were encountered: