Skip to content

[DOCS] Fix link to Stack upgrade guide #5286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 26, 2022
Merged

[DOCS] Fix link to Stack upgrade guide #5286

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/release-notes/1.3.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
=== Breaking changes

* Make ECK IPv6 compatible {pull}3654[#3654] (issues: {issue}2830[#2830], {issue}3649[#3649]) - in an accompanying change `network.publish_host` setting value was switched to DNS name. This might result in non-ready Pods being included in the headless service for Elasticsearch StatefulSets.
* Enforce a strict upgrade order between stack components {pull}3537[#3537] (issues: {issue}2600[#2600], {issue}3535[#3535]) - ECK will prevent updates that would violate link:https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html#upgrade-order-elastic-stack[Elastic Stack upgrade process] version constraints. ECK 1.3.0 won't apply any updates to resources that are in violation of those constraints until versions are updated to (at least) the same minors.
* Enforce a strict upgrade order between stack components {pull}3537[#3537] (issues: {issue}2600[#2600], {issue}3535[#3535]) - ECK will prevent updates that would violate link:https://www.elastic.co/guide/en/elastic-stack/7.17/upgrading-elastic-stack.html#upgrade-order-elastic-stack[Elastic Stack upgrade process] version constraints. ECK 1.3.0 won't apply any updates to resources that are in violation of those constraints until versions are updated to (at least) the same minors.
* Add set-default-security-context flag to handle runAs user in ES 8.0+ {pull}3342[#3342] (issue: {issue}2791[#2791]) - a default security context is added to Elasticsearch 8.0+ Pods in order to deal with volume filesystem permissions. Can be disabled through operator configuration on environments with restricted security settings (Openshift, for example).
* Allow init containers modifications {pull}3336[#3336] (issue: {issue}2306[#2306]) - modifications to built-in init containers will be merged with the defaults instead of completely replacing them.

Expand Down