Update Helm release elasticsearch to v21 #49
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
3 times, most recently
from
12b9264 to
617b32e
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
617b32e to
5f99742
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
3 times, most recently
from
8d5449c to
a6d54ef
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
a6d54ef to
fed86e4
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
2 times, most recently
from
386c828 to
a65e065
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
a65e065 to
d9f62d6
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
d9f62d6 to
19e19d8
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
19e19d8 to
cb4c9de
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
cb4c9de to
eaf60ee
Compare
WalkthroughThe update modifies the configuration for the application by changing the version number of the Elasticsearch dependency in the YAML configuration file. The version has been updated from 19.17.0 to 21.4.7 while all other fields remain unchanged. Changes
Sequence Diagram(s)(No sequence diagram necessary as the changes only involve a configuration update.) Poem
📜 Recent review detailsConfiguration used: .coderabbit.yaml ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🔇 Additional comments (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
charts/dave/Chart.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
charts/dave/Chart.yaml(1 hunks)
🔇 Additional comments (1)
charts/dave/Chart.yaml (1)
16-32: Major version upgrade requires careful review of breaking changes.This is a significant version jump from 19.x.x to 21.x.x. Please ensure:
- Review the release notes for any breaking changes
- Verify compatibility with other dependencies (postgresql, backend, frontend, etc.)
- Consider testing the upgrade path in a non-production environment first
Let's check for any compatibility information or known issues:
✅ Verification successful
🌐 Web query:
What are the breaking changes in Elasticsearch Helm chart version 21.x.x compared to 19.x.x?💡 Result:
The transition from Elasticsearch Helm chart version 19.x.x to 21.x.x (specifically Bitnami-maintained charts) introduces several breaking changes based on license updates and architectural shifts:
Key Breaking Changes
1. License Model Shift
- Elastic License Adoption: Starting with 19.21.2, Elasticsearch components moved under the Elastic License (non-Open Source), replacing OSS distributions[4][7]. This affects deployments relying on open-source Elasticsearch/Kibana versions.
2. Security Enabled by Default
- Mandatory TLS & Authentication: From version 8.0.0+, security features (TLS encryption and authentication) are auto-configured by default[1].
- Older configurations disabling security (
security.enabled=false) are no longer supported.- Charts now auto-generate credentials/TLS certificates unless custom ones are provided via
security.*values[1].
3. Service Account Token for Kibana
- Kibana now requires a service account token (instead of the
elasticsuperuser) to connect to secured Elasticsearch clusters[1].- The Helm chart automatically creates this token via a
pre-installhook[1].
4. Node Roles Configuration
- In 8.5.1+, Elasticsearch node roles are defined as a simple list (e.g.,
["master", "data"]) instead of a dictionary[1].- All roles from Elasticsearch’s documentation are supported.
5. Kubernetes Version Support
- Support for Kubernetes 1.19 and 1.20 was dropped[1].
- Added support for 1.23 and 1.24[1].
6. APM Server OSS Removal
- APM Server OSS distribution was removed starting with 8.0.0[1]. Only non-OSS versions are available.
7.Helm Chart Repository Changes
- The original Elastic Helm charts repository was archived after 8.5.1[1], with users migrating to alternatives like Bitnami’s charts.
Upgrade Considerations
- Cluster Migration: Existing clusters with security disabled require reconfiguration to enable TLS/authentication.
- Kibana Connection: Ensure service account tokens are correctly generated during upgrades.
- Node Roles: Update role definitions from dictionaries to lists.
- License Compliance: Verify compliance with the Elastic License for production use[4][7].
For detailed steps, refer to the Elastic Helm Charts migration guide[1].
Citations:
- 1: https://github.com/elastic/helm-charts/blob/main/BREAKING_CHANGES.md
- 2: https://docs.dremio.com/current/release-notes/version-240-release/
- 3: https://docs.camunda.io/docs/self-managed/operational-guides/update-guide/820-to-830/
- 4: https://artifacthub.io/packages/helm/bitnami/elasticsearch/19.21.2
- 5: https://github.com/elastic/helm-charts/releases
- 6: https://doc.nuxeo.com/nxdoc/upgrade-from-lts-2019-to-lts-2021/
- 7: https://artifacthub.io/packages/helm/bitnami/elasticsearch/21.0.0
- 8: https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html
- 9: https://artifacthub.io/packages/helm/bitnami/elasticsearch
- 10: https://discuss.elastic.co/t/elastic-version-moves-very-fast/323338
Elasticsearch Helm Chart Upgrade – Breaking Changes Confirmed
The breaking changes outlined in the web query are indeed significant for version 21.x.x compared to 19.x.x. Please keep the following in mind:
- License Model Shift: The chart now uses the Elastic License instead of an OSS distribution, which may affect deployments expecting open-source behavior.
- Security Enabled by Default: TLS encryption and authentication are auto-configured. Any previous configuration that disabled security will no longer work.
- Kibana Connectivity: Kibana now requires a service account token instead of the default
elasticsuperuser, necessitating updates to your connection settings.- Node Roles Configuration: Node roles are now defined as a simple list rather than a dictionary, meaning your configuration for node roles might need adjustment.
- Kubernetes Version Support: Support for Kubernetes versions 1.19 and 1.20 has been dropped in favor of newer versions (1.23, 1.24).
- APM Server OSS Removal: If you rely on APM Server OSS, note that only non-OSS variants are available.
Ensure compatibility with your other dependencies (postgresql, backend, frontend, etc.) and test the upgrade path in a non-production environment before rolling it out to production.
charts/dave/Chart.yaml
Outdated
| @@ -16,7 +16,7 @@ sources: | |||
| dependencies: | |||
| - name: elasticsearch | |||
| repository: https://charts.bitnami.com/bitnami | |||
| version: 19.17.0 | |||
| version: 21.4.5 | |||
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Version discrepancy detected between PR description and code.
The PR description mentions updating to version 21.4.4, but the code shows 21.4.5. Please verify the intended version.
Let's check the latest available versions and their release dates:
🏁 Script executed:
#!/bin/bash
# Description: Check latest versions of the elasticsearch helm chart
# Get latest versions from Bitnami charts repository
curl -s https://raw.githubusercontent.com/bitnami/charts/master/bitnami/elasticsearch/Chart.yaml | grep "version:"Length of output: 165
Discrepancy: PR Description vs. Updated Version
The file charts/dave/Chart.yaml now shows the dependency version as 21.4.5, which aligns with the version provided upstream (as confirmed by the Bitnami repository). However, the PR objectives mention version 21.4.4. Please verify and update the PR description/documentation to reflect the correct intended version.
- File:
charts/dave/Chart.yaml - Impact: Version mismatch in documentation versus code, which could lead to confusion during testing and deployment.
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
eaf60ee to
1b55ea8
Compare
renovate
bot
force-pushed
the
renovate/elasticsearch-21.x
branch
from
1b55ea8 to
2c498c0
Compare
This PR contains the following updates:
19.17.0->21.4.7Release Notes
bitnami/charts (elasticsearch)
v21.4.7v21.4.6v21.4.5v21.4.4v21.4.3v21.4.2v21.4.1v21.4.0v21.3.26v21.3.25v21.3.24v21.3.23v21.3.22v21.3.21v21.3.20v21.3.19v21.3.18v21.3.17v21.3.16v21.3.15v21.3.14v21.3.13v21.3.12v21.3.11v21.3.10v21.3.9v21.3.8v21.3.7v21.3.6v21.3.5v21.3.4v21.3.3v21.3.2v21.3.1v21.3.0v21.2.8v21.2.7v21.2.6v21.2.5v21.2.4v21.2.3v21.2.2v21.2.1v21.2.0v21.1.3v21.1.2v21.1.1v21.1.0v21.0.7v21.0.6v21.0.5v21.0.4v21.0.3v21.0.2v21.0.1v21.0.0v20.0.4v20.0.3v20.0.2v20.0.1v20.0.0v19.21.2v19.21.1v19.21.0v19.20.0v19.19.4v19.19.3v19.19.2v19.19.1v19.18.0v19.17.6v19.17.5v19.17.4v19.17.3v19.17.2Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.