Skip to content

Commit f462028

Browse files
committed
some eck docs moved to security and IA and landing pages updated
1 parent fab0447 commit f462028

25 files changed

+395
-314
lines changed

deploy-manage/deploy/cloud-on-k8s/configure-deployments.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ Additionally, the following topics apply to both {{es}} and {{kib}}, and in some
2929

3030
ECK also facilitates configuration and operation activities with advanced features, such as:
3131

32+
* [**Secure settings**](/deploy-manage/security/k8s-secure-settings.md): Configure {{es}} and {{kib}} keystore settings through Kubernetes secrets.
33+
3234
* [**Elastic Stack configuration policies**](elastic-stack-configuration-policies.md): Organize your {{es}} and {{kib}} configuration settings through `StackConfigPolicy` resources that can be referenced within your deployments. This helps to keep your manifests simplified.
3335

3436
::::{important}

deploy-manage/deploy/cloud-on-k8s/configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The following guides cover common ECK configuration tasks:
2727

2828
* [Service meshes](./service-meshes.md): Connect ECK and managed Elastic Stack applications to some of the most popular [service mesh](https://www.cncf.io/blog/2017/04/26/service-mesh-critical-component-cloud-native-stack/) implementations in the Kubernetes ecosystem.
2929

30-
* [Network policies](./network-policies.md): Use [Kubernetes network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) to isolate pods by restricting incoming and outgoing network connections to a trusted set of sources and destinations.
30+
* [Network policies](./../../security/k8s-network-policies.md): Use [Kubernetes network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) to isolate pods by restricting incoming and outgoing network connections to a trusted set of sources and destinations.
3131

3232
* [](./webhook-namespace-selectors.md): Restrict the namespaces that the validation webhook applies to, allowing multiple operators to coexist efficiently in the same cluster.
3333

deploy-manage/deploy/cloud-on-k8s/elastic-stack-configuration-policies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Starting from ECK `2.6.1` and Elasticsearch `8.6.1`, Elastic Stack configuration
3535
Additionally with ECK `2.11.0` it is possible to configure Kibana as well using Elastic Stack configuration policies, the following settings can be configured for Kibana:
3636

3737
* [Kibana Configuration](kibana://reference/configuration-reference/general-settings.md) (configuration settings for Kibana that will go into `kibana.yml`)
38-
* [Kibana Secure Settings](k8s-kibana-secure-settings.md)
38+
* [Kibana Secure Settings](../../security/k8s-secure-settings.md)
3939

4040
A policy can be applied to one or more Elasticsearch clusters or Kibana instances in any namespace managed by the ECK operator. Configuration policy settings applied by the ECK operator are immutable through the Elasticsearch REST API. It is currently not allowed to configure an Elasticsearch cluster or Kibana instance with more than one policy.
4141

@@ -65,7 +65,7 @@ At least one of `spec.elasticsearch` or `spec.kibana` needs to be defined with a
6565
* `spec.kibana` describes the settings to configure for Kibana.
6666

6767
* `config` are the settings that go into the `kibana.yml` file.
68-
* `secureSettings` is a list of Secrets containing Secure Settings to inject into the keystore(s) of the Kibana instance(s) to which this policy applies, similar to the [Kibana Secure Settings](k8s-kibana-secure-settings.md).
68+
* `secureSettings` is a list of Secrets containing Secure Settings to inject into the keystore(s) of the Kibana instance(s) to which this policy applies, similar to the [Kibana Secure Settings](../../security/k8s-secure-settings.md).
6969

7070

7171
The following fields are optional:

deploy-manage/deploy/cloud-on-k8s/elasticsearch-configuration.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Before deploying and running ECK in production, review the basic and advanced se
2222
* [Node configuration](node-configuration.md): Configure the `elasticsearch.yml` of your {{es}} nodes.
2323
* [Volume claim templates](volume-claim-templates.md): Configure storage in your {{es}} nodes.
2424
* [Virtual memory](virtual-memory.md): Methods to accomplish {{es}} virtual memory system configuration requirement.
25+
* [Secure settings](/deploy-manage/security/secure-settings.md): Configure the {{es}} keystore through Kubernetes secrets.
2526
* [Settings managed by ECK](settings-managed-by-eck.md): List of {{es}} settings that you shouldn't update.
2627
* [Custom configuration files and plugins](custom-configuration-files-plugins.md): Add extra configuration files or install plugins to your {{es}} nodes.
2728
* [Init containers for plugin downloads](init-containers-for-plugin-downloads.md): Use Kubernetes init containers to install plugins before starting {{es}}.
@@ -38,7 +39,7 @@ Before deploying and running ECK in production, review the basic and advanced se
3839
## TLS/SSL Certificates
3940

4041
* [Secure HTTP communications](/deploy-manage/security/secure-http-communications.md): Customize the service and TLS certificates used for transport traffic.
41-
* [Transport settings](transport-settings.md): Customize the service and TLS certificates used for transport traffic.
42+
* [Transport settings](../../security/k8s-transport-settings.md): Customize the service and TLS certificates used for transport traffic.
4243

4344
## Traffic handling
4445

@@ -48,8 +49,6 @@ Before deploying and running ECK in production, review the basic and advanced se
4849

4950
Other sections of the documentation also include relevant configuration options for your {{es}} cluster:
5051

51-
* [Secure settings](/deploy-manage/security/secure-settings.md)
52-
5352
* [Users and roles](/deploy-manage/users-roles.md)
5453

5554
* [Snapshots](../../tools/snapshot-and-restore/cloud-on-k8s.md)

deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If you already looked at the [Elasticsearch on ECK](elasticsearch-configuration.
1313
* [Customize the Pod configuration](#k8s-kibana-pod-configuration)
1414
* [Customize the product configuration](#k8s-kibana-configuration)
1515
* [Manage HTTP settings](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-configuration)
16-
* [Use secure settings](k8s-kibana-secure-settings.md)
16+
* [Use secure settings](../../security/k8s-secure-settings.md)
1717
* [Install {{kib}} plugins](k8s-kibana-plugins.md)
1818

1919
## Pod configuration [k8s-kibana-pod-configuration]
@@ -97,7 +97,7 @@ kubectl get secret my-kibana-kb-config -o jsonpath='{ .data.kibana\.yml }' | bas
9797
::::
9898

9999

100-
You can provide your own encryption keys using a secure setting, as described in [Secure settings](k8s-kibana-secure-settings.md).
100+
You can provide your own encryption keys using a secure setting, as described in [Secure settings](../../security/k8s-secure-settings.md).
101101

102102
::::{note}
103103
While most reconfigurations of your {{kib}} instances are carried out in rolling upgrade fashion, all version upgrades will cause {{kib}} downtime. This happens because you can only run a single version of {{kib}} at any given time. For more information, check [Upgrade {{kib}}](/deploy-manage/upgrade/deployment-or-cluster.md).

deploy-manage/deploy/cloud-on-k8s/k8s-kibana-es.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Refer to [*Connect to external Elastic resources*](connect-to-external-elastic-r
4747

4848
## Using secure settings [k8s_using_secure_settings]
4949

50-
For example, use the [secure settings](k8s-kibana-secure-settings.md) mechanism to securely store the default `elastic` user’s `$PASSWORD` credential of the external {{es}} cluster as set under [Deploy an {{es}} cluster](elasticsearch-deployment-quickstart.md):
50+
For example, use the [secure settings](../../security/k8s-secure-settings.md) mechanism to securely store the default `elastic` user’s `$PASSWORD` credential of the external {{es}} cluster as set under [Deploy an {{es}} cluster](elasticsearch-deployment-quickstart.md):
5151

5252
```shell
5353
kubectl create secret generic kibana-elasticsearch-credentials --from-literal=elasticsearch.password=$PASSWORD

deploy-manage/deploy/cloud-on-k8s/k8s-kibana-secure-settings.md

Lines changed: 0 additions & 40 deletions
This file was deleted.

deploy-manage/deploy/cloud-on-k8s/kibana-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The following sections describe how to customize a {{kib}} deployment to suit yo
2121
* [{{kib}} Configuration](k8s-kibana-advanced-configuration.md#k8s-kibana-configuration)
2222
* [Scaling out a {{kib}} deployment](k8s-kibana-advanced-configuration.md#k8s-kibana-scaling)
2323

24-
* [Secure settings](k8s-kibana-secure-settings.md)
24+
* [Secure settings](../../security/k8s-secure-settings.md#k8s-kibana-secure-settings)
2525
* [HTTP Configuration](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-configuration)
2626

2727
* [Load balancer settings and TLS SANs](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-publish)

0 commit comments

Comments
 (0)