Update consul Docker tag to v1.13.1 #289
Merged
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.
This PR contains the following updates:
1.12.3
->1.13.1
Release Notes
hashicorp/consul
v1.13.1
Compare Source
BUG FIXES:
v1.13.0
Compare Source
BREAKING CHANGES:
telemetry { disable_compat_1.9 = (true|false) }
has been removed. Before upgrading you should remove this flag from your config if the flag is being used. [GH-13532]FEATURES:
consul version
commandsto report this. Agent also reports build date in log on startup. [GH-13357]
Sign
[GH-12787]valid config file, e.g., config delete -filename intention-allow.hcl [GH-13677]
destination
field to theservice-default
config entry that allows routing egress trafficthrough a terminating gateway in transparent proxy mode without modifying the catalog. [GH-13613]
ingress-gateway
,mesh
,service-intentions
andservice-resolver
config entry events. [GH-13658]IMPROVEMENTS:
merge-central-config
query parameter support added to/catalog/node-services/:node-name
API, to view a fully resolved service definition (especially when not written into the catalog that way). [GH-13450]merge-central-config
query parameter support added to/catalog/node-services/:node-name
API, to view a fully resolved service definition (especially when not written into the catalog that way). [GH-2046]merge-central-config
query parameter support added to some catalog and health endpoints to view a fully resolved service definition (especially when not written into the catalog that way). [GH-13001]This was the only missing piece to ensure all mesh services are validated for a port (or socketpath) specification on catalog registration. [GH-12881]
consul connect envoy
command.Adds the
-prometheus-ca-file
,-prometheus-ca-path
,-prometheus-cert-file
and-prometheus-key-file
flags. [GH-13481]max_inbound_connections
setting to service-defaults for limiting the number of concurrent inbound connections to each service instance. [GH-13143]consul.raft.thread.main.saturation
andconsul.raft.thread.fsm.saturation
metrics to measure approximate saturation of the Raft goroutines [GH-12865]BUG FIXES:
acl token read
is used with the-self
and-expanded
flags, return an error instead of panicking [GH-13787]connect: Terminating gateways with a wildcard service entry should no longer pick up connect services as upstreams. [GH-13958]
v1.12.4
Compare Source
BUG FIXES:
acl token read
is used with the-self
and-expanded
flags, return an error instead of panicking [GH-13787]connect: Terminating gateways with a wildcard service entry should no longer pick up connect services as upstreams. [GH-13958]
Configuration
📅 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 has been generated by Mend Renovate. View repository job log here.