8000 Release notes for 1.7.0 by zaharidichev · Pull Request #2321 · linkerd/linkerd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Release notes for 1.7.0 #2321

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

Merged
merged 2 commits into from
Aug 29, 2019
Merged

Conversation

zaharidichev
Copy link
Member

Release notes PR. Comments on style are more than welcome.

Signed-off-by: Zahari Dichev zaharidichev@gmail.com

Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
Copy link
Contributor
@dadjeibaah dadjeibaah left a comment

Choose a reason for hiding this comment

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

Thanks for typing this up. I went through and made some updates to organization. Check out the diff below.

diff --git a/CHANGES.md b/CHANGES.md
index 14a44f1a9..c09c105e8 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -1,34 +1,40 @@
 ## 1.7.0 2019-08-27
-Linkerd 1.7.0 includes a number of memory leak fixes for both linkerd as
-well ass `grpc-runtime` library. Additionally this release includes
-improvements for SNI-enabled tls communication, support for arbitrarily
-larger messages in HTTP/1 and HTTP/2 as well as improved container
-support.
-
-
-Full release notes:
-* Enable streaming in Consul HTTP client to allow for arbitrarily large
-responses from Consul
-* Updates Linkerd's JDK version for better container support
-* Adds support for including metadata from Consul responses into Namerd's
-response
-* Removes `maxRequestKB` and `maxResponseKB` from Linkerd's configuration
-options in favor of `streamAfterContentLengthKB`
-* Introduces a router parameter called `maxCallDepth` that prevents infinite
-proxy routing
-* Fixes an issue where Linkerd cannot connect to SNI servers that are addressed
-via ipv4/6
-* Fixes a number of direct and heap memory leaks in Linkerd's HTTP/2 module
-* Fixes an issue causing users of `grpc-runtime` library to experience native
-memory leaks
-* Adds support for limiting the maximum size of the `l5d-err` header values by
-using `maxErrResponseKB` in an HTTP router
-* Fixes an issue were some `socketOptions` were being ignored when partially
-configured
+Linkerd 1.7.0 includes a number of memory leak fixes for Linkerd and its
+underlying `grpc-runtime` module. This release includes improvements for 
+SNI-enabled TLS communication, support for streaming arbitrarily large HTTP
+requests and responses in HTTP/1 and HTTP/2 as well an upgraded JDK for 
+improved Docker container support.
 
 A special thank you to [Fantayeneh](https://github.com/fantayeneh) for their
 awesome work on [#2315](https://github.com/linkerd/linkerd/pull/2315)
 
+Full release notes:
+* **Breaking Change**
+  * Removes `maxRequestKB` and `maxResponseKB` from Linkerd's configuration
+    options in favor of `streamAfterContentLengthKB`. 
+    
+* Consul
+  * Enables streaming in the HTTP client used in the `io.l5d.consul` namer
+    to allow for arbitrarily large responses from Consul
+  * Adds support for including metadata received from Consul responses to 
+    include in Namerd's responses on `io.l5d.mesh` and `io.l5d.httpController`
+    interfaces
+* Linkerd Configuration
+  * Introduces a router parameter called `maxCallDepth` that prevents unbounded
+    cyclic proxy request routing
+  * Adds support for limiting the maximum size of `l5d-err` header values by
+    using `maxErrResponseKB` in an HTTP router
+  * Fixes an issue were some `socketOptions` were being ignored when partially
+    configured
+* TLS
+  * Fixes an issue where Linkerd can't connect to SNI servers that are addressed
+    via IPv4 and IPv6
+* HTTP/2
+  * Fixes a number of direct and heap memory leaks in Linkerd's HTTP/2 module
+  * Fixes an issue causing users of `grpc-runtime` module to experience direct
+    memory leaks
+* Updates Linkerd's JDK version for improved container support
+
 ## 1.6.4 2019-07-01
 Linkerd 1.6.4 updates the finagle version to 19.5.1 and adds support for
 configuring message response sizes from when using consul.  
diff --git a/project/Base.scala b/project/Base.scala
index 5f99c522b..cdc1b240f 100644
--- a/project/Base.scala
+++ b/project/Base.scala
@@ -32,7 +32,7 @@ object Base {
 class Base extends Build {
   import Base._
 
-  val headVersion = "1.6.4"
+  val headVersion = "1.7.0"
   val openJdkVersion = "8u212"
   val openJ9Version = "jdk8u212-b04_openj9-0.14.2"
 

@zaharidichev zaharidichev requested a review from adleong as a code owner August 28, 2019 13:21
@zaharidichev zaharidichev force-pushed the zd/1.7.0-release-notes branch from 6fa20d4 to 90f3cf2 Compare August 28, 2019 15:05
Copy link
Member
@adleong adleong left a comment

Choose a reason for hiding this comment

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

Great!


Full release notes:
* **Breaking Change**
* Removes `maxRequestKB` and `maxResponseKB` from Linkerd's configuration
Copy link
Member

Choose a reason for hiding this comment

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

I might add a bit more context here about this change:

These parameters were primarily intended to limit the amount of memory Linkerd used when buffering requests. The streamAfterContentLengthKB parameter achieves this more efficiently by streaming large messages instead of buffering them.

CHANGES.md Outdated
* Consul
* Enables streaming in the HTTP client used in the `io.l5d.consul` namer
to allow for arbitrarily large responses from Consul
* Adds support for including metadata received from Consul responses to
Copy link
@admc admc Aug 28, 2019

Choose a reason for hiding this comment

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

This is a bit choppy to read.

  • Support for the inclusion of Consul response metadata in Namerd 'io.l5d.mesh and 'io.l5d.httpController' responses.

Or something?

Copy link
Member Author

Choose a reason for hiding this comment

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

wow... this is indeed quite bad...

Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
@zaharidichev zaharidichev force-pushed the zd/1.7.0-release-notes branch from 90f3cf2 to e77f89d Compare August 28, 2019 17:49
@dadjeibaah dadjeibaah merged commit f0775c5 into linkerd:master Aug 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0