From 70c074e207376d8031d5d80d5330f94dc23a5cd4 Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi Date: Wed, 2 Feb 2022 08:51:32 +0100 Subject: [PATCH 1/4] Fix read more --- .../agent-fleet.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc b/docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc index afaf9f2c3b..9739195dbf 100644 --- a/docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc +++ b/docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc @@ -397,7 +397,7 @@ To deploy Elastic Agent in clusters with the Pod Security Policy admission contr [id="{p}-elastic-agent-fleet-configuration-customize-fleet-server-service"] === Customize Fleet Server Service -By default, ECK creates a Service for Fleet Server that Elastic Agents can connect through. You can customize it using the `http` configuration element. You can read more about link:k8s-services.html[making changes] to the Service and link:k8s-tls-certificates.html[customizing] TLS configuration in the documentation. +By default, ECK creates a Service for Fleet Server that Elastic Agents can connect through. You can customize it using the `http` configuration element. Check more information on how to link:k8s-services.html[make changes] to the Service and link:k8s-tls-certificates.html[customize] the TLS configuration. [id="{p}-elastic-agent-fleet-configuration-override-default-fleet-configuration-settings"] === Override default Fleet configuration settings From eacb62fa32f89fe4aa67c090864f57ea48349cac Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi Date: Wed, 2 Feb 2022 14:08:52 +0100 Subject: [PATCH 2/4] Fix more read occurrences --- docs/design/0005-configurable-operator.md | 2 +- docs/operating-eck/installing-eck.asciidoc | 2 +- .../security/saml-authentication.asciidoc | 2 +- docs/quickstart.asciidoc | 2 +- docs/release-notes/1.7.0.asciidoc | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/design/0005-configurable-operator.md b/docs/design/0005-configurable-operator.md index cfb10b4c62..fc8773565f 100644 --- a/docs/design/0005-configurable-operator.md +++ b/docs/design/0005-configurable-operator.md @@ -135,7 +135,7 @@ Pros: Cons: * Need for a "hybrid" version to deploy everything in a single restricted namespace (eg. "default"), which is a bit confusing -* The global-operator needs elevated permissions on the cluster (eg. read access to all secrets) +* The global-operator needs elevated permissions on the cluster (eg. get access to all secrets) * One might want to use several global-operators on a single cluster * One operator per namespace might lead to deploy too many operators diff --git a/docs/operating-eck/installing-eck.asciidoc b/docs/operating-eck/installing-eck.asciidoc index aaa5dfb431..472cc709d5 100644 --- a/docs/operating-eck/installing-eck.asciidoc +++ b/docs/operating-eck/installing-eck.asciidoc @@ -112,7 +112,7 @@ helm show values elastic/eck-operator [id="{p}-migrate-to-helm"] === Migrate an existing installation to Helm -CAUTION: Migrating an existing installation to Helm is essentially an upgrade operation and any <<{p}-beta-to-ga-rolling-restart,caveats associated with normal operator upgrades>> are applicable. Read the <<{p}-ga-upgrade,upgrade documentation>> before proceeding. +CAUTION: Migrating an existing installation to Helm is essentially an upgrade operation and any <<{p}-beta-to-ga-rolling-restart,caveats associated with normal operator upgrades>> are applicable. Check the <<{p}-ga-upgrade,upgrade documentation>> before proceeding. You can migrate an existing operator installation to Helm by adding the `meta.helm.sh/release-name`, `meta.helm.sh/release-namespace` annotations and the `app.kubernetes.io/managed-by` label to all the resources you want to be adopted by Helm. You _must_ do this for the Elastic Custom Resource Definitions (CRD) because deleting them would trigger the deletion of all deployed Elastic applications as well. All other resources are optional and can be deleted. diff --git a/docs/orchestrating-elastic-stack-applications/security/saml-authentication.asciidoc b/docs/orchestrating-elastic-stack-applications/security/saml-authentication.asciidoc index bc7e77fcfe..242839af3e 100644 --- a/docs/orchestrating-elastic-stack-applications/security/saml-authentication.asciidoc +++ b/docs/orchestrating-elastic-stack-applications/security/saml-authentication.asciidoc @@ -11,7 +11,7 @@ The Elastic Stack supports SAML single sign-on (SSO) into Kibana, using Elastics NOTE: Elastic Stack SSO requires a valid Enterprise license or Enterprise trial license. Check <<{p}-licensing,the license documentation>> for more details about managing licenses. -TIP: Make sure you read the complete link:https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-stack.html[Configuring SAML single sign-on on the Elastic Stack] guide before setting up SAML SSO for Kibana and Elasticsearch deployments managed by ECK. +TIP: Make sure you check the complete link:https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-stack.html[Configuring SAML single sign-on on the Elastic Stack] guide before setting up SAML SSO for Kibana and Elasticsearch deployments managed by ECK. == Add a SAML realm to X-Pack security settings diff --git a/docs/quickstart.asciidoc b/docs/quickstart.asciidoc index a8e19d2bac..03375fad69 100644 --- a/docs/quickstart.asciidoc +++ b/docs/quickstart.asciidoc @@ -29,7 +29,7 @@ include::supported-versions.asciidoc[] [id="{p}-deploy-eck"] == Deploy ECK in your Kubernetes cluster -IMPORTANT: Read the <<{p}-upgrading-eck,upgrade notes>> first if you are attempting to upgrade an existing ECK deployment. +IMPORTANT: Check the <<{p}-upgrading-eck,upgrade notes>> first if you are attempting to upgrade an existing ECK deployment. [NOTE] ==== diff --git a/docs/release-notes/1.7.0.asciidoc b/docs/release-notes/1.7.0.asciidoc index c189aae355..c0de0f28c8 100644 --- a/docs/release-notes/1.7.0.asciidoc +++ b/docs/release-notes/1.7.0.asciidoc @@ -35,7 +35,7 @@ [float] === Bug fixes -* Beats: allow unprivileged Pods to read configuration file {pull}4572[#4572] (issue: {issue}4562[#4562]) +* Beats: allow unprivileged Pods to access the configuration file {pull}4572[#4572] (issue: {issue}4562[#4562]) * Fix heap memory parsing with trailing white spaces {pull}4571[#4571] (issue: {issue}4564[#4564]) * Detect admission registration API version {pull}4569[#4569] (issue: {issue}4555[#4555]) From 82be42f9ad8276aebb7f098e4e8a0bfeb631888f Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com> Date: Thu, 3 Feb 2022 12:36:29 +0100 Subject: [PATCH 3/4] Update docs/release-notes/1.7.0.asciidoc Co-authored-by: Thibault Richard --- docs/release-notes/1.7.0.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/1.7.0.asciidoc b/docs/release-notes/1.7.0.asciidoc index c0de0f28c8..c189aae355 100644 --- a/docs/release-notes/1.7.0.asciidoc +++ b/docs/release-notes/1.7.0.asciidoc @@ -35,7 +35,7 @@ [float] === Bug fixes -* Beats: allow unprivileged Pods to access the configuration file {pull}4572[#4572] (issue: {issue}4562[#4562]) +* Beats: allow unprivileged Pods to read configuration file {pull}4572[#4572] (issue: {issue}4562[#4562]) * Fix heap memory parsing with trailing white spaces {pull}4571[#4571] (issue: {issue}4564[#4564]) * Detect admission registration API version {pull}4569[#4569] (issue: {issue}4555[#4555]) From 9e6a8a3702719f36ff7464f7b3054003f18b21af Mon Sep 17 00:00:00 2001 From: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com> Date: Thu, 3 Feb 2022 12:36:35 +0100 Subject: [PATCH 4/4] Update docs/design/0005-configurable-operator.md Co-authored-by: Thibault Richard --- docs/design/0005-configurable-operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/0005-configurable-operator.md b/docs/design/0005-configurable-operator.md index fc8773565f..cfb10b4c62 100644 --- a/docs/design/0005-configurable-operator.md +++ b/docs/design/0005-configurable-operator.md @@ -135,7 +135,7 @@ Pros: Cons: * Need for a "hybrid" version to deploy everything in a single restricted namespace (eg. "default"), which is a bit confusing -* The global-operator needs elevated permissions on the cluster (eg. get access to all secrets) +* The global-operator needs elevated permissions on the cluster (eg. read access to all secrets) * One might want to use several global-operators on a single cluster * One operator per namespace might lead to deploy too many operators