add official communication

README.md

@@ -6,49 +6,64 @@
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
 
-- [Charts](#charts)
 - [Supported Configurations](#supported-configurations)
   - [Stack Versions](#stack-versions)
   - [Kubernetes Versions](#kubernetes-versions)
   - [Helm Versions](#helm-versions)
-- [ECK](#eck)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 <!-- Use this to update TOC: -->
 <!-- docker run --entrypoint doctoc --rm -it -v $(pwd):/usr/src jorgeandrada/doctoc README.md --github --no-title -->
 
-
-## Charts
-
 These Helm charts are designed to be a lightweight way to configure Elastic
 official Docker images.
 
+> **Warning**
+> When it comes to running the Elastic on Kubernetes infrastructure, we
+> recommend [Elastic Cloud on Kubernetes][] (ECK) as the best way to run and manage
+> the Elastic Stack.
+>
+> ECK offers many operational benefits for both our basic-tier and our
+> enterprise-tier customers, such as spinning up cluster nodes that were lost on
+> failed infrastructure, seamless upgrades, rolling cluster changes, and much
+> much more.
+>
+> With the release of the Elastic Stack Helm charts for Elastic version 8.5.1,
+> we are handing over the ongoing maintenance of our Elastic Stack Helm charts
+> to the community and contributors. This repository will finally be archived
+> after 6 months time. Elastic Stacks deployed on Kubernetes through Helm charts
+> will still be fully supported under EOL limitations.
+>
+> Since we want to provide an even better experience for our customers by
+> running the Elastic Stack on Kubernetes, we will continue maintaining the
+> Helm charts applicable to ECK Custom Resources. These charts can be found in
+> the [ECK repository][eck-charts].
+>
+> Helm charts will currently be maintained for ECK Enterprise-tier customers,
+> however, we encourage the community to engage with the existing Helm charts
+> for the Elastic Stack and continue supporting their ongoing maintenance.
+
+
 ## Supported Configurations
 
 We recommend that the Helm chart version is aligned to the version of the
-product you want to deploy. This will ensure that you are using a chart version
+product you want to deploy, when a chart release exists for the given stack
+version. This will ensure that you are using a chart version
 that has been tested against the corresponding production version.
 This will also ensure that the documentation and examples for the chart will
 work with the version of the product, you are installing.
 
 For example, if you want to deploy an Elasticsearch `7.7.1` cluster, use the
 corresponding `7.7.1` [tag][elasticsearch-771].
 
-However, we are not releasing new charts versions for each new patch version of
-the Elastic products, so if a chart for the latest patch version doesn't exist,
-you can use the latest chart with the same **MAJOR.MINOR** version and override
-the Docker image tag to the latest patch version with the `imageTag` value.
+However, we don't expect to release new charts versions, so if a chart for the
+latest patch version doesn't exist, you can use the latest chart with the same
+**MAJOR.MINOR** version and override the Docker image tag to the latest patch
+version with the `imageTag` value.
 
 For example, if you want to deploy an Elasticsearch `7.17.5` cluster, use the
 corresponding `7.17.3` [tag][elasticsearch-7173], with `imageTag=7.17.5` value.
 
-The `master` version of these charts is intended to support the latest
-pre-release versions of our products, and therefore may or may not work with
-current released versions.
-Note that only the released charts coming from [Elastic Helm repo][] or
-[GitHub releases][] are supported.
-
-
 ### Stack Versions
 
 | Chart                                      | Latest 8 Version                            | Latest 7 Version                             | Latest 6 Version                   |
@@ -71,24 +86,12 @@ exact versions are defined under `KUBERNETES_VERSIONS` in
 While we are checking backward compatibility, the charts are only tested with
 Helm version mentioned in [helm-tester Dockerfile][] (currently 3.9.4).
 
-
-## ECK
-
-In addition to these Helm charts, Elastic also provides
-[Elastic Cloud on Kubernetes][] which is based on [Operator pattern][] and is
-Elastic recommended way to deploy Elasticsearch, Kibana, and APM Server on
-Kubernetes. There is a dedicated Helm chart for ECK which can be found
-[in ECK repo][eck-chart] ([documentation][eck-chart-doc]).
-
-
 [apm-6]: https://github.com/elastic/helm-charts/tree/6.8/apm-server/README.md
 [apm-7]: https://github.com/elastic/helm-charts/tree/7.17/apm-server/README.md
 [apm-8]: https://github.com/elastic/helm-charts/tree/main/apm-server/README.md
 [currently tested]: https://devops-ci.elastic.co/job/elastic+helm-charts+main/
-[eck-chart-doc]: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-install-helm.html
-[eck-chart]: https://github.com/elastic/cloud-on-k8s/tree/master/deploy
+[eck-charts]: https://github.com/elastic/cloud-on-k8s/tree/master/deploy
 [elastic cloud on kubernetes]: https://github.com/elastic/cloud-on-k8s
-[elastic helm repo]: https://helm.elastic.co
 [elasticsearch-6]: https://github.com/elastic/helm-charts/tree/6.8/elasticsearch/README.md
 [elasticsearch-7]: https://github.com/elastic/helm-charts/tree/7.17/elasticsearch/README.md
 [elasticsearch-7173]: https://github.com/elastic/helm-charts/tree/7.17.3/elasticsearch/
@@ -97,7 +100,6 @@ Kubernetes. There is a dedicated Helm chart for ECK which can be found
 [filebeat-6]: https://github.com/elastic/helm-charts/tree/6.8/filebeat/README.md
 [filebeat-7]: https://github.com/elastic/helm-charts/tree/7.17/filebeat/README.md
 [filebeat-8]: https://github.com/elastic/helm-charts/tree/main/filebeat/README.md
-[github releases]: https://github.com/elastic/helm-charts/releases
 [helm-tester Dockerfile]: https://github.com/elastic/helm-charts/blob/main/helpers/helm-tester/Dockerfile
 [helpers/matrix.yml]: https://github.com/elastic/helm-charts/blob/main/helpers/matrix.yml
 [kibana-6]: https://github.com/elastic/helm-charts/tree/6.8/kibana/README.md
@@ -109,4 +111,3 @@ Kubernetes. There is a dedicated Helm chart for ECK which can be found
 [metricbeat-6]: https://github.com/elastic/helm-charts/tree/6.8/metricbeat/README.md
 [metricbeat-7]: https://github.com/elastic/helm-charts/tree/7.17/metricbeat/README.md
 [metricbeat-8]: https://github.com/elastic/helm-charts/tree/main/metricbeat/README.md
-[operator pattern]: https://kubernetes.io/docs/concepts/extend-kubernetes/operator/

apm-server/README.md

@@ -5,10 +5,30 @@
 This Helm chart is a lightweight way to configure and run our official
 [APM Server Docker image][].
 
-**Warning**: This functionality is in alpha and is subject to change.
-The design and code is less mature than official GA features and is being
-provided as-is with no warranties. Alpha features are not subject to the support
-SLA of official GA features (see [supported configurations][] for more details).
+> **Warning**
+> When it comes to running the Elastic on Kubernetes infrastructure, we
+> recommend [Elastic Cloud on Kubernetes][] (ECK) as the best way to run and manage
+> the Elastic Stack.
+>
+> ECK offers many operational benefits for both our basic-tier and our
+> enterprise-tier customers, such as spinning up cluster nodes that were lost on
+> failed infrastructure, seamless upgrades, rolling cluster changes, and much
+> much more.
+>
+> With the release of the Elastic Stack Helm charts for Elastic version 8.5.1,
+> we are handing over the ongoing maintenance of our Elastic Stack Helm charts
+> to the community and contributors. This repository will finally be archived
+> after 6 months time. Elastic Stacks deployed on Kubernetes through Helm charts
+> will still be fully supported under EOL limitations.
+>
+> Since we want to provide an even better experience for our customers by
+> running the Elastic Stack on Kubernetes, we will continue maintaining the
+> Helm charts applicable to ECK Custom Resources. These charts can be found in
+> the [ECK repository][eck-charts].
+>
+> Helm charts will currently be maintained for ECK Enterprise-tier customers,
+> however, we encourage the community to engage with the existing Helm charts
+> for the Elastic Stack and continue supporting their ongoing maintenance.
 
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
@@ -129,14 +149,16 @@ Please check [CONTRIBUTING.md][] before any contribution or for any questions
 about our development and testing process.
 
 [7.x]: https://github.com/elastic/helm-charts/releases
-[BREAKING_CHANGES.md]: https://github.com/elastic/helm-charts/blob/main/BREAKING_CHANGES.md
-[CHANGELOG.md]: https://github.com/elastic/helm-charts/blob/main/CHANGELOG.md
-[CONTRIBUTING.md]: https://github.com/elastic/helm-charts/blob/main/CONTRIBUTING.md
 [affinity]: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
 [annotations]: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
 [apm server docker image]: https://www.elastic.co/guide/en/apm/server/current/running-on-docker.html
-[environment variables]: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/#using-environment-variables-inside-of-your-config
+[BREAKING_CHANGES.md]: https://github.com/elastic/helm-charts/blob/main/BREAKING_CHANGES.md
+[CHANGELOG.md]: https://github.com/elastic/helm-charts/blob/main/CHANGELOG.md
+[CONTRIBUTING.md]: https://github.com/elastic/helm-charts/blob/main/CONTRIBUTING.md
+[eck-charts]: https://github.com/elastic/cloud-on-k8s/tree/master/deploy
+[elastic cloud on kubernetes]: https://github.com/elastic/cloud-on-k8s
 [environment from variables]: https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables
+[environment variables]: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/#using-environment-variables-inside-of-your-config
 [examples]: https://github.com/elastic/helm-charts/tree/main/apm-server/examples
 [examples/security]: https://github.com/elastic/helm-charts/tree/main/apm-server/examples/security
 [horizontal pod autoscaler]: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/

elasticsearch/README.md

@@ -5,6 +5,31 @@
 This Helm chart is a lightweight way to configure and run our official
 [Elasticsearch Docker image][].
 
+> **Warning**
+> When it comes to running the Elastic on Kubernetes infrastructure, we
+> recommend [Elastic Cloud on Kubernetes][] (ECK) as the best way to run and manage
+> the Elastic Stack.
+>
+> ECK offers many operational benefits for both our basic-tier and our
+> enterprise-tier customers, such as spinning up cluster nodes that were lost on
+> failed infrastructure, seamless upgrades, rolling cluster changes, and much
+> much more.
+>
+> With the release of the Elastic Stack Helm charts for Elastic version 8.5.1,
+> we are handing over the ongoing maintenance of our Elastic Stack Helm charts
+> to the community and contributors. This repository will finally be archived
+> after 6 months time. Elastic Stacks deployed on Kubernetes through Helm charts
+> will still be fully supported under EOL limitations.
+>
+> Since we want to provide an even better experience for our customers by
+> running the Elastic Stack on Kubernetes, we will continue maintaining the
+> Helm charts applicable to ECK Custom Resources. These charts can be found in
+> the [ECK repository][eck-charts].
+>
+> Helm charts will currently be maintained for ECK Enterprise-tier customers,
+> however, we encourage the community to engage with the existing Helm charts
+> for the Elastic Stack and continue supporting their ongoing maintenance.
+
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
@@ -390,32 +415,35 @@ lifecycle:
 Please check [CONTRIBUTING.md][] before any contribution or for any questions
 about our development and testing process.
 
-[7.x]: https://github.com/elastic/helm-charts/releases
 [#1186 (comment)]: https://github.com/elastic/helm-charts/pull/1186#discussion_r631166442
-[BREAKING_CHANGES.md]: https://github.com/elastic/helm-charts/blob/main/BREAKING_CHANGES.md
-[CHANGELOG.md]: https://github.com/elastic/helm-charts/blob/main/CHANGELOG.md
-[CONTRIBUTING.md]: https://github.com/elastic/helm-charts/blob/main/CONTRIBUTING.md
+[7.x]: https://github.com/elastic/helm-charts/releases
 [alternate scheduler]: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/#specify-schedulers-for-pods
 [annotations]: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
 [anti-affinity]: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
+[BREAKING_CHANGES.md]: https://github.com/elastic/helm-charts/blob/main/BREAKING_CHANGES.md
+[CHANGELOG.md]: https://github.com/elastic/helm-charts/blob/main/CHANGELOG.md
 [cluster.name]: https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster.name.html
 [clustering and node discovery]: https://github.com/elastic/helm-charts/blob/main/elasticsearch/README.md#clustering-and-node-discovery
 [config example]: https://github.com/elastic/helm-charts/blob/main/elasticsearch/examples/config/values.yaml
+[CONTRIBUTING.md]: https://github.com/elastic/helm-charts/blob/main/CONTRIBUTING.md
 [curator]: https://www.elastic.co/guide/en/elasticsearch/client/curator/current/snapshot.html
 [custom docker image]: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#_c_customized_image
 [deploys statefulsets serially]: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies
 [discovery.zen.minimum_master_nodes]: https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-settings.html#minimum_master_nodes
 [docker for mac]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/docker-for-mac
+[eck-charts]: https://github.com/elastic/cloud-on-k8s/tree/master/deploy
+[elastic cloud on kubernetes]: https://github.com/elastic/cloud-on-k8s
 [elasticsearch cluster health status params]: https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html#request-params
 [elasticsearch docker image]: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html
-[environment variables]: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/#using-environment-variables-inside-of-your-config
 [environment from variables]: https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables
+[environment variables]: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/#using-environment-variables-inside-of-your-config
 [examples]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/
 [examples/multi]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/multi
 [examples/security]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/security
 [gke]: https://cloud.google.com/kubernetes-engine
 [helm]: https://helm.sh
 [helm/charts stable]: https://github.com/helm/charts/tree/master/stable/elasticsearch/
+[hostAliases]: https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
 [how to install plugins guide]: https://github.com/elastic/helm-charts/blob/main/elasticsearch/README.md#how-to-install-plugins
 [how to use the keystore]: https://github.com/elastic/helm-charts/blob/main/elasticsearch/README.md#how-to-use-the-keystore
 [http.port]: https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#_settings
@@ -424,17 +452,16 @@ about our development and testing process.
 [ingress]: https://kubernetes.io/docs/concepts/services-networking/ingress/
 [java options]: https://www.elastic.co/guide/en/elasticsearch/reference/current/jvm-options.html
 [jvm heap size]: https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html
-[hostAliases]: https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
 [kind]: https://github.com/elastic/helm-charts/tree/main//elasticsearch/examples/kubernetes-kind
 [labels]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
 [lifecycle hooks]: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/
 [loadBalancer annotations]: https://kubernetes.io/docs/concepts/services-networking/service/#ssl-support-on-aws
 [loadBalancer externalTrafficPolicy]: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
 [loadBalancer]: https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
 [maxUnavailable]: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
+[microk8s]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/microk8s
 [migration guide]: https://github.com/elastic/helm-charts/blob/main/elasticsearch/examples/migration/README.md
 [minikube]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/minikube
-[microk8s]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/microk8s
 [multi]: https://github.com/elastic/helm-charts/tree/main/elasticsearch/examples/multi/
 [network.host elasticsearch setting]: https://www.elastic.co/guide/en/elasticsearch/reference/current/network.host.html
 [node affinity settings]: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#node-affinity-beta-feature