From 7e8b5f9eebf28ca5e97a502366a2ede3072895e9 Mon Sep 17 00:00:00 2001 From: Kaarina Tungseth Date: Tue, 14 Dec 2021 15:06:05 -0600 Subject: [PATCH] Remove CentOS (#121128) --- docs/settings/reporting-settings.asciidoc | 2 +- docs/setup/configuring-reporting.asciidoc | 2 +- docs/setup/docker.asciidoc | 12 ++++++------ docs/setup/install.asciidoc | 2 +- docs/setup/install/rpm.asciidoc | 6 +++--- .../reporting-production-considerations.asciidoc | 2 +- .../reporting/reporting-troubleshooting.asciidoc | 2 +- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/settings/reporting-settings.asciidoc b/docs/settings/reporting-settings.asciidoc index af10430ef8d01e..cfdaf0e1b2d752 100644 --- a/docs/settings/reporting-settings.asciidoc +++ b/docs/settings/reporting-settings.asciidoc @@ -139,7 +139,7 @@ Specifies the browser to use to capture screenshots. This setting exists for bac When <> is set to `chromium` (default) you can also specify the following settings. `xpack.reporting.capture.browser.chromium.disableSandbox`:: -It is recommended that you research the feasibility of enabling unprivileged user namespaces. An exception is if you are running {kib} in Docker because the container runs in a user namespace with the built-in seccomp/bpf filters. For more information, refer to <>. Defaults to `false` for all operating systems except Debian, Red Hat Linux, and CentOS, which use `true`. +It is recommended that you research the feasibility of enabling unprivileged user namespaces. An exception is if you are running {kib} in Docker because the container runs in a user namespace with the built-in seccomp/bpf filters. For more information, refer to <>. Defaults to `false` for all operating systems except Debian and Red Hat Linux, which use `true`. `xpack.reporting.capture.browser.chromium.proxy.enabled`:: Enables the proxy for Chromium to use. When set to `true`, you must also specify the `xpack.reporting.capture.browser.chromium.proxy.server` setting. Defaults to `false`. diff --git a/docs/setup/configuring-reporting.asciidoc b/docs/setup/configuring-reporting.asciidoc index 38bf2955fb56e6..ca6bf19f404e5d 100644 --- a/docs/setup/configuring-reporting.asciidoc +++ b/docs/setup/configuring-reporting.asciidoc @@ -14,7 +14,7 @@ To enable users to manually and automatically generate reports, install the repo Make sure the {kib} server operating system has the appropriate packages installed for the distribution. -If you are using CentOS/RHEL systems, install the following packages: +If you are using RHEL operating systems, install the following packages: * `ipa-gothic-fonts` * `xorg-x11-fonts-100dpi` diff --git a/docs/setup/docker.asciidoc b/docs/setup/docker.asciidoc index 0aa6c680a77618..df140dbd00b701 100644 --- a/docs/setup/docker.asciidoc +++ b/docs/setup/docker.asciidoc @@ -1,11 +1,11 @@ [[docker]] === Install {kib} with Docker ++++ -Install with Docker +Install with Docker ++++ -Docker images for Kibana are available from the Elastic Docker registry. The -base image is https://hub.docker.com/_/centos/[centos:7]. +Docker images for {kib} are available from the Elastic Docker registry. The +base image is https://hub.docker.com/_/kibana[kibana]. A list of all published Docker images and tags is available at https://www.docker.elastic.co[www.docker.elastic.co]. The source code is in @@ -126,9 +126,9 @@ docker rm kib-01 [discrete] [[configuring-kibana-docker]] -=== Configure Kibana on Docker +=== Configure {kib} on Docker -The Docker images provide several methods for configuring Kibana. The +The Docker images provide several methods for configuring {kib}. The conventional approach is to provide a `kibana.yml` file as described in {kibana-ref}/settings.html[Configuring Kibana], but it's also possible to use environment variables to define settings. @@ -137,7 +137,7 @@ environment variables to define settings. [[bind-mount-config]] ==== Bind-mounted configuration -One way to configure Kibana on Docker is to provide `kibana.yml` via bind-mounting. +One way to configure {kib} on Docker is to provide `kibana.yml` via bind-mounting. With `docker-compose`, the bind-mount can be specified like this: ["source","yaml",subs="attributes"] diff --git a/docs/setup/install.asciidoc b/docs/setup/install.asciidoc index cb47210cb3f089..8b64bdf5fe2a2e 100644 --- a/docs/setup/install.asciidoc +++ b/docs/setup/install.asciidoc @@ -33,7 +33,7 @@ our Debian repository. `rpm`:: -The `rpm` package is suitable for installation on Red Hat, Centos, SLES, +The `rpm` package is suitable for installation on Red Hat, SLES, OpenSuSE and other RPM-based systems. RPMs may be downloaded from the Elastic website or from our RPM repository. + diff --git a/docs/setup/install/rpm.asciidoc b/docs/setup/install/rpm.asciidoc index 0ef714c73b9bac..996175c724293b 100644 --- a/docs/setup/install/rpm.asciidoc +++ b/docs/setup/install/rpm.asciidoc @@ -7,11 +7,11 @@ The RPM for Kibana can be <> or from our <>. It can be used to install -Kibana on any RPM-based system such as OpenSuSE, SLES, Centos, Red Hat, +Kibana on any RPM-based system such as OpenSuSE, SLES, Red Hat, and Oracle Enterprise. NOTE: RPM install is not supported on distributions with old versions of RPM, -such as SLES 11 and CentOS 5. Please see <> instead. +such as SLES 11. Refer to <> instead. This package contains both free and subscription features. <> to try out all of the features. @@ -85,7 +85,7 @@ sudo yum install kibana <1> sudo dnf install kibana <2> sudo zypper install kibana <3> -------------------------------------------------- -<1> Use `yum` on CentOS and older Red Hat based distributions. +<1> Use `yum` on older Red Hat based distributions. <2> Use `dnf` on Fedora and other newer Red Hat distributions. <3> Use `zypper` on OpenSUSE based distributions diff --git a/docs/user/production-considerations/reporting-production-considerations.asciidoc b/docs/user/production-considerations/reporting-production-considerations.asciidoc index 32752cbe69ab8c..9f5207d910c0c2 100644 --- a/docs/user/production-considerations/reporting-production-considerations.asciidoc +++ b/docs/user/production-considerations/reporting-production-considerations.asciidoc @@ -20,7 +20,7 @@ For an additional layer of security, use the sandbox. The Chromium sandbox uses ==== Linux sandbox The Linux sandbox depends on user namespaces, which were introduced with the 3.8 Linux kernel. However, many distributions don't have user namespaces enabled by default, or they require the CAP_SYS_ADMIN capability. The {report-features} -automatically disable the sandbox when it is running on Debian and CentOS, as additional steps are required to enable +automatically disable the sandbox when it is running on Debian because additional steps are required to enable unprivileged usernamespaces. In these situations, you'll see the following message in your {kib} startup logs: `Chromium sandbox provides an additional layer of protection, but is not supported for your OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'.` diff --git a/docs/user/reporting/reporting-troubleshooting.asciidoc b/docs/user/reporting/reporting-troubleshooting.asciidoc index 4b59cad38fd9a1..fab01083a80a8b 100644 --- a/docs/user/reporting/reporting-troubleshooting.asciidoc +++ b/docs/user/reporting/reporting-troubleshooting.asciidoc @@ -154,7 +154,7 @@ In this case, try increasing the memory for the {kib} instance to 2GB. [[reporting-troubleshooting-arm-systems]] === ARM systems -Chromium is not compatible with ARM RHEL/CentOS. +Chromium is not compatible with ARM RHEL. [float] [[reporting-troubleshooting-maps-ems]]