Skip to content
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.

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

Release notes and highlights for 2.15 #8172

Merged
merged 10 commits into from
Nov 11, 2024

Conversation

rhr323
Copy link
Contributor

@rhr323 rhr323 commented Nov 1, 2024

Adding Release notes and Release highlights for the upcoming 2.15.0 release.

@rhr323 rhr323 added >docs Documentation exclude-from-release-notes Exclude this PR from appearing in the release notes v2.15.0 labels Nov 1, 2024
@rhr323 rhr323 marked this pull request as ready for review November 1, 2024 14:28
@@ -0,0 +1,21 @@
[[release-highlights-2.15.0]]
== 2.15.0 release highlights

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add information about the role mapping fix in 8.16 (as a known issue maybe), or is that not strictly related to this ECK release?

Copy link
Collaborator

@pebrc pebrc Nov 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would probably still include the existing known issue. And we need to amend it to mention that the issue is resolved in 8.16. We can do all of that in a separate PR though.


[float]
[id="{p}-2150-latest-k8s-support"]
=== Support for Kubernetes 1.31
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m not sure if it’s worth mentioning here, since we didn’t make any changes specific to the latest K8s release.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we didn't usually mention this.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for leaving this out to stay consistent with previous messaging.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback. I'll remove this part from the highlights.

If we simplify the Wolfi adoption section, maybe we could position this as a ‘maintenance’ release focused on enhancements, documentation improvements, and dependency updates. This would make the release highlights shorter than usual, without calling out specific changes. What do you think, @pebrc, @barkbay?

[float]
=== Enhancements

* Clarify high availability recommendations in Elasticsearch orchestration docs {pull}8151[#8151]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this one should be in the Documentation improvements section?

* Log when k8s resources are created/updated/deleted successfully {pull}8094[#8094]
* More meaningful error in readiness script {pull}8091[#8091] (issue: {issue}8088[#8088])
* Update Maps Images to multi-arch {pull}8085[#8085] (issue: {issue}8034[#8034])
* Add missing metricsets {pull}8048[#8048] (issue: {issue}7277[#7277])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's maybe clarify what metricset, and that this is in the context of stack monitoring?

* More meaningful error in readiness script {pull}8091[#8091] (issue: {issue}8088[#8088])
* Update Maps Images to multi-arch {pull}8085[#8085] (issue: {issue}8034[#8034])
* Add missing metricsets {pull}8048[#8048] (issue: {issue}7277[#7277])
* Do not parse the version twice {pull}8005[#8005]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this one is a refactoring, not really a feature enhancement?


[float]
[id="{p}-2150-latest-k8s-support"]
=== Support for Kubernetes 1.31
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we didn't usually mention this.

[id="{p}-2150-wolfi-images"]
=== Wolfi images

ECK has transitioned to using https://github.com/wolfi-dev[Wolfi images], an open-source project aimed at delivering a secure, minimal base image for containerized applications. By adopting Wolfi, ECK strengthens its security posture, significantly lowering the potential for CVEs (Common Vulnerabilities and Exposures) and reducing the overall attack surface. This shift aligns with best practices for container security, providing a more robust foundation for running workloads reliably and securely.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering if this wording oversells the wolfi adoption for ECK somewhat. Given that we were already running on distroless the attack surface was already pretty reduced.

Also we still publish a UBI variant which is where most of the vulnerabilities are.

@rhr323
Copy link
Contributor Author

rhr323 commented Nov 5, 2024

Hey @pebrc , @barkbay ,

I have simplified the release highlights to a single sentence. Let me know what you think. Also updated the release notes according to the feedback received. Thanks!


* Ensure esclient is closed after each reconcile. {pull}8175[#8175] (issue: {issue}8174[#8174])
* Fix resetting service type to default when not specified {pull}8165[#8165] (issue: {issue}8161[#8161])
* Fix logstash templating issue {pull}8087[#8087] (issue: {issue}8000[#8000])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix logstash templating issue {pull}8087[#8087] (issue: {issue}8000[#8000])
* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])

* Fix logstash templating issue {pull}8087[#8087] (issue: {issue}8000[#8000])
* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
* Handle Kibana basepath updates for fleet {pull}8053[#8053] (issue: {issue}7909[#7909])
* Fix eck-stack kibana examples {pull}8041[#8041]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix eck-stack kibana examples {pull}8041[#8041]
* Fix eck-stack kibana examples in Helm chart {pull}8041[#8041]

Or prefix Helm related fixes with [Helm]?

Comment on lines 48 to 63
* fix(deps): update module go.uber.org/automaxprocs to v1.6.0 {pull}8107[#8107]
* fix(deps): update module github.com/prometheus/common to v0.60.0 {pull}8106[#8106]
* fix(deps): update module github.com/masterminds/sprig/v3 to v3.3.0 {pull}8105[#8105]
* fix(deps): update module github.com/hashicorp/vault/api to v1.15.0 {pull}8104[#8104]
* fix(deps): update module cloud.google.com/go/storage to v1.44.0 {pull}8103[#8103]
* fix(deps): update k8s controller tools {pull}8101[#8101]
* chore(deps): update wolfi/go to v1.23.2 and wolfi/static {pull}8083[#8083]
* fix(deps): update module github.com/gobuffalo/flect to v1.0.3 {pull}8071[#8071]
* fix(deps): update k8s controller libraries to v0.31.1 {pull}8056[#8056]
* chore(deps): update registry.access.redhat.com/ubi9/ubi-minimal docker tag to v9.4-1227.1726694542 {pull}8055[#8055]
* fix(deps): update module github.com/prometheus/client_golang to v1.20.4 {pull}8045[#8045]
* fix(deps): update module go.elastic.co/apm/v2 to v2.6.2 {pull}8036[#8036]
* fix(deps): update module dario.cat/mergo to v1.0.1 {pull}8013[#8013]
* fix(deps): update module github.com/google/go-containerregistry to v0.20.2 {pull}7998[#7998]
* Bump github.com/docker/docker from 26.1.4+incompatible to 26.1.5+incompatible {pull}7996[#7996]
* fix(deps): update module github.com/gkampitakis/go-snaps to v0.5.7 {pull}7986[#7986]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I used to sort this as an attempt to make it more readable


* Log when k8s resources are created/updated/deleted successfully {pull}8094[#8094]
* More meaningful error in readiness script {pull}8091[#8091] (issue: {issue}8088[#8088])
* Update Maps Images to multi-arch {pull}8085[#8085] (issue: {issue}8034[#8034])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Update Maps Images to multi-arch {pull}8085[#8085] (issue: {issue}8034[#8034])
* Update Elastic Maps Server images to multi-arch {pull}8085[#8085] (issue: {issue}8034[#8034])

[float]
=== Bug fixes

* Ensure esclient is closed after each reconcile. {pull}8175[#8175] (issue: {issue}8174[#8174])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Ensure esclient is closed after each reconcile. {pull}8175[#8175] (issue: {issue}8174[#8174])
* Ensure Elasticsearch client is closed after each reconciliation. {pull}8175[#8175] (issue: {issue}8174[#8174])


* Ensure esclient is closed after each reconcile. {pull}8175[#8175] (issue: {issue}8174[#8174])
* Fix resetting service type to default when not specified {pull}8165[#8165] (issue: {issue}8161[#8161])
* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])
* Fix Logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])

* Ensure esclient is closed after each reconcile. {pull}8175[#8175] (issue: {issue}8174[#8174])
* Fix resetting service type to default when not specified {pull}8165[#8165] (issue: {issue}8161[#8161])
* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])
* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
* Move '$leading_path' variable definition in eck-operator Helm chart {pull}8075[#8075]

* Fix resetting service type to default when not specified {pull}8165[#8165] (issue: {issue}8161[#8161])
* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])
* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
* Handle Kibana basepath updates for fleet {pull}8053[#8053] (issue: {issue}7909[#7909])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Handle Kibana basepath updates for fleet {pull}8053[#8053] (issue: {issue}7909[#7909])
* Support Kibana basepath in associations {pull}8053[#8053] (issue: {issue}7909[#7909])

* Fix logstash templating issue in Helm chart {pull}8087[#8087] (issue: {issue}8000[#8000])
* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
* Handle Kibana basepath updates for fleet {pull}8053[#8053] (issue: {issue}7909[#7909])
* Fix eck-stack kibana examples in Helm chart {pull}8041[#8041]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix eck-stack kibana examples in Helm chart {pull}8041[#8041]
* Fix eck-stack Kibana examples in Helm chart {pull}8041[#8041]

* Move '$leading_path' variable definition in eck-operator {pull}8075[#8075]
* Handle Kibana basepath updates for fleet {pull}8053[#8053] (issue: {issue}7909[#7909])
* Fix eck-stack kibana examples in Helm chart {pull}8041[#8041]
* Add watcher for statefulsets in agent controller {pull}8011[#8011]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Add watcher for statefulsets in agent controller {pull}8011[#8011]
* Add watcher for StatefulSets in Elastic Agent controller {pull}8011[#8011]

@rhr323 rhr323 merged commit 31861ea into elastic:main Nov 11, 2024
5 checks passed
@rhr323 rhr323 deleted the 2.15-release-notes-and-highlights branch November 11, 2024 11:48
rhr323 added a commit to rhr323/cloud-on-k8s that referenced this pull request Nov 11, 2024
* added release notes and lightlights for 2.15

* change title updates

* remove known issues section

* removed leftover comment

* simplified release highlights

* release notes regenerated

* metricset pr description update

* release notes updates

* lines sorted

* release notes regenerated

(cherry picked from commit 31861ea)
@rhr323
Copy link
Contributor Author

rhr323 commented Nov 11, 2024

💚 All backports created successfully

Status Branch Result
2.15

Questions ?

Please refer to the Backport tool documentation

rhr323 added a commit that referenced this pull request Nov 11, 2024
* added release notes and lightlights for 2.15

* change title updates

* remove known issues section

* removed leftover comment

* simplified release highlights

* release notes regenerated

* metricset pr description update

* release notes updates

* lines sorted

* release notes regenerated

(cherry picked from commit 31861ea)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs Documentation exclude-from-release-notes Exclude this PR from appearing in the release notes v2.15.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants