Skip to content

Commit

Permalink
[7.x] [DOCS] Adds the 7.14.0 release notes (#107058) (#107466)
Browse files Browse the repository at this point in the history
* [DOCS] Adds the 7.14.0 release notes

* [DOCS] Edits machine learning PR descriptions

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Larry Gregory <[email protected]>

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Larry Gregory <[email protected]>

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Mike Côté <[email protected]>

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Mike Côté <[email protected]>

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Mike Côté <[email protected]>

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Mike Côté <[email protected]>

* Updates from review comments

* Adds best practices section

* Update docs/CHANGELOG.asciidoc

Co-authored-by: Mike Côté <[email protected]>

* Fixes errors

Co-authored-by: lcawl <[email protected]>
Co-authored-by: Larry Gregory <[email protected]>
Co-authored-by: Mike Côté <[email protected]>
  • Loading branch information
4 people authored Aug 2, 2021
1 parent 2fcf3e4 commit 26ce797
Show file tree
Hide file tree
Showing 7 changed files with 566 additions and 8 deletions.
558 changes: 558 additions & 0 deletions docs/CHANGELOG.asciidoc

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion docs/settings/alert-action-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
Alerts and actions are enabled by default in {kib}, but require you configure the following in order to use them:

. <<using-kibana-with-security,Set up {kib} to work with {stack} {security-features}>>.
. <<configuring-tls-kib-es,Set up TLS encryption between {kib} and {es}>>.
. {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[Encrypt traffic between {kib} and {es}].
. If you are using an *on-premises* Elastic Stack deployment, <<general-alert-action-settings,specify a value for `xpack.encryptedSavedObjects.encryptionKey`>>.

You can configure the following settings in the `kibana.yml` file.
Expand Down
2 changes: 1 addition & 1 deletion docs/settings/fleet-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ See the {fleet-guide}/index.html[{fleet}] docs for more information.
|===
| `xpack.fleet.agents.fleet_server.hosts`
| Hostnames used by {agent} for accessing {fleet-server}.
| `xpack.fleet.agents.elasticsearch.hosts`
| [[xpack-fleet-agents-elasticsearch-hosts]]`xpack.fleet.agents.elasticsearch.hosts`
| Hostnames used by {agent} for accessing {es}.
| `xpack.fleet.agents.elasticsearch.ca_sha256`
| Hash pin used for certificate verification. The pin is a base64-encoded
Expand Down
6 changes: 3 additions & 3 deletions docs/setup/settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,13 @@ that disables certain unnecessary and potentially insecure capabilities in
the browser. It is strongly recommended that you keep the default CSP rules
that ship with {kib}.

| `csp.script_src:`
| [[csp-script-src]]`csp.script_src:`
| Add sources for the https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src[Content Security Policy `script-src` directive].

| `csp.worker_src:`
| [[csp-worker-src]]`csp.worker_src:`
| Add sources for the https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/worker-src[Content Security Policy `worker-src` directive].

| `csp.style_src:`
| [[csp-style-src]]`csp.style_src:`
| Add sources for the https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/style-src[Content Security Policy `style-src` directive].

| `csp.connect_src:`
Expand Down
2 changes: 1 addition & 1 deletion docs/user/alerting/alerting-setup.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ If you are using an *on-premises* Elastic Stack deployment:

If you are using an *on-premises* Elastic Stack deployment with <<using-kibana-with-security, *security*>>:

* You must enable Transport Layer Security (TLS) for communication <<configuring-tls-kib-es, between {es} and {kib}>>. {kib} alerting uses <<api-keys, API keys>> to secure background rule checks and actions, and API keys require {ref}/configuring-tls.html#tls-http[TLS on the HTTP interface]. A proxy will not suffice.
* You must enable Transport Layer Security (TLS) for communication {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[between {es} and {kib}]. {kib} alerting uses <<api-keys, API keys>> to secure background rule checks and actions, and API keys require {ref}/configuring-tls.html#tls-http[TLS on the HTTP interface]. A proxy will not suffice.
* If you have enabled TLS and are still unable to access Alerting, ensure that you have not {ref}/security-settings.html#api-key-service-settings[explicitly disabled API keys].

[float]
Expand Down
2 changes: 1 addition & 1 deletion docs/user/monitoring/monitoring-kibana.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ valid user ID and password in the `elasticsearch.username` and
`elasticsearch.password` settings in the `kibana.yml` file. These values are
used when {kib} sends monitoring data to the production cluster.

.. <<configuring-tls-kib-es,Configure encryption for traffic between {kib} and {es}>>.
.. {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[Encrypt traffic between {kib} and {es}].

. <<start-stop,Start {kib}>>.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ To configure {kib} and {es} to use mutual TLS authentication:

. <<using-kibana-with-security,Set up {kib} to work with {stack} {security-features} with a username and password>>.

. <<configuring-tls-kib-es,Set up TLS encryption between {kib} and {es}>>.
. {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[Encrypt traffic between {kib} and {es}].
+
This entails generating a "server certificate" for {es} to use on the HTTP layer.

Expand Down

0 comments on commit 26ce797

Please sign in to comment.