chore(nsq): bump version to 1.3.0#30
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NSQ upgrade notes
This bumps the BeeInventor NSQ Helm chart from
1.2.7to1.3.0. The underlying NSQ appimage moves from
nsqio/nsq:v1.2.1tonsqio/nsq:v1.3.0.Upstream NSQ
v1.3.0changelog highlights:gobindata/ Go 1.16 support.nsqd: adds TLS root CA usage for nsqauth requests.nsqd: adds Unix socket listener support for TCP/HTTP/HTTPS.nsqd: adds/debug/freememory, richer/info, TLS 1.3 support, optional HTTP/HTTPSlistener disabling, and related fixes.
nsqadmin: updates frontend JS support to ES2020, adds paused-topic labeling, and fixesUI graph/counter issues.
statsd/memstats panic fixes.
Source: https://github.com/nsqio/nsq/releases/tag/v1.3.0
Why no values changes
No
values.yamlchange is needed for this chart bump.The chart already leaves
image.tagunset, and the templates default the runtime image tagfrom
.Chart.AppVersion, so bumpingappVersionto1.3.0automatically rendersnsqio/ nsq:v1.3.0. Pinningimage.tagin values would duplicate the same version and createfuture drift risk.
The NSQ
v1.3.0changes are either build-time maintenance, bug fixes, or optional runtimefeatures behind new flags. Our existing chart values do not configure those optional flags,
and the current ports, services, lookupd wiring, persistence, replicas, and metrics settings
remain valid.