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

chore(deps): update hashicorp/consul docker tag to v1.20.0 #78

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 20, 2023

This PR contains the following updates:

Package Update Change
hashicorp/consul (source) minor 1.11.2 -> 1.20.0

Release Notes

hashicorp/consul (hashicorp/consul)

v1.20.0

Compare Source

SECURITY:

  • Explicitly set 'Content-Type' header to mitigate XSS vulnerability. [GH-21704]
  • Implement HTML sanitization for user-generated content to prevent XSS attacks in the UI. [GH-21711]
  • UI: Remove codemirror linting due to package dependency [GH-21726]
  • Upgrade Go to use 1.22.7. This addresses CVE
    CVE-2024-34155 [GH-21705]
  • Upgrade to support aws/aws-sdk-go v1.55.5 or higher. This resolves CVEs
    CVE-2020-8911 and
    CVE-2020-8912. [GH-21684]
  • ui: Pin a newer resolution of Braces [GH-21710]
  • ui: Pin a newer resolution of Codemirror [GH-21715]
  • ui: Pin a newer resolution of Markdown-it [GH-21717]
  • ui: Pin a newer resolution of ansi-html [GH-21735]

FEATURES:

  • grafana: added the dashboards service-to-service dashboard, service dashboard, and consul dataplane dashboard [GH-21806]
  • server: remove v2 tenancy, catalog, and mesh experiments [GH-21592]

IMPROVEMENTS:

  • security: upgrade ubi base image to 9.4 [GH-21750]
  • connect: Add Envoy 1.31 and 1.30 to support matrix [GH-21616]

BUG FIXES:

  • jwt-provider: change dns lookup family from the default of AUTO which would prefer ipv6 to ALL if LOGICAL_DNS is used or PREFER_IPV4 if STRICT_DNS is used to gracefully handle transitions to ipv6. [GH-21703]

v1.19.2

Compare Source

SECURITY:

  • ui: Upgrade modules with d3-color as a dependency to address denial of service issue in d3-color < 3.1.0 [GH-21588]

IMPROVEMENTS:

  • Use Envoy's default for a route's validate_clusters option, which is false. This fixes a case where non-existent clusters could cause a route to no longer route to any of its backends, including existing ones. [GH-21587]

BUG FIXES:

  • api-gateway: (Enterprise only) ensure clusters are properly created for JWT providers with a remote URI for the JWKS endpoint [GH-21604]

v1.19.1

Compare Source

SECURITY:

IMPROVEMENTS:

  • mesh: update supported envoy version 1.29.5 in addition to 1.28.4, 1.27.6. [GH-21277]

BUG FIXES:

  • core: Fix multiple incorrect type conversion for potential overflows [GH-21251]
  • core: Fix panic runtime error on AliasCheck [GH-21339]
  • dns: Fix a regression where DNS SRV questions were returning duplicate hostnames instead of encoded IPs.
    This affected Nomad integrations with Consul. [GH-21361]
  • dns: Fix a regression where DNS tags using the standard lookup syntax, tag.name.service.consul, were being disregarded. [GH-21361]
  • dns: Fixes a spam log message "Failed to parse TTL for prepared query..."
    that was always being logged on each prepared query evaluation. [GH-21381]
  • terminating-gateway: (Enterprise Only) Fixed issue where enterprise metadata applied to linked services was the terminating-gateways enterprise metadata and not the linked services enterprise metadata. [GH-21382]
  • txn: Fix a bug where mismatched Consul server versions could result in undetected data loss for when using newer Transaction verbs. [GH-21519]

v1.19.0

Compare Source

BREAKING CHANGES:

  • telemetry: State store usage metrics with a double consul element in the metric name have been removed. Please use the same metric without the second consul instead. As an example instead of consul.consul.state.config_entries use consul.state.config_entries [GH-20674]

SECURITY:

FEATURES:

  • dns: queries now default to a refactored DNS server that is v1 and v2 Catalog compatible.
    Use v1dns in the experiments agent config to disable.
    The legacy server will be removed in a future release of Consul.
    See the Consul 1.19.x Release Notes for removed DNS features. [GH-20715]
  • gateways: api-gateway can leverage listener TLS certificates available on the gateway's local filesystem by specifying the public certificate and private key path in the new file-system-certificate configuration entry [GH-20873]

IMPROVEMENTS:

  • dns: new version was not supporting partition or namespace being set to 'default' in CE version. [GH-21230]
  • mesh: update supported envoy version 1.29.4 in addition to 1.28.3, 1.27.5, 1.26.8. [GH-21142]
  • upgrade go version to v1.22.4. [GH-21265]
  • Upgrade github.com/envoyproxy/go-control-plane to 0.12.0. [GH-20973]
  • dns: DNS-over-grpc when using consul-dataplane now accepts partition, namespace, token as metadata to default those query parameters.
    consul-dataplane v1.5+ will send this information automatically. [GH-20899]
  • snapshot: Add consul snapshot decode CLI command to output a JSON object stream of all the snapshots data. [GH-20824]
  • telemetry: Add telemetry.disable_per_tenancy_usage_metrics in agent configuration to disable setting tenancy labels on usage metrics. This significantly decreases CPU utilization in clusters with many admin partitions or namespaces.
  • telemetry: Improved the performance usage metrics emission by not outputting redundant metrics. [GH-20674]

DEPRECATIONS:

  • snapshot agent: (Enterprise only) Top level single snapshot destinations local_storage, aws_storage, azure_blob_storage, and google_storage in snapshot agent configuration files are now deprecated. Use the backup_destinations config object instead.

BUG FIXES:

v1.18.2

Compare Source

Enterprise LTS: Consul Enterprise 1.18 is a Long-Term Support (LTS) release.

SECURITY:

IMPROVEMENTS:

  • gateways: service defaults configuration entries can now be used to set default upstream limits for mesh-gateways [GH-20945]
  • connect: Add ability to disable Auto Host Header Rewrite on Terminating Gateway at the service level [GH-20802]

BUG FIXES:

  • dns: fix a bug with sameness group queries in DNS where responses did not respect DefaultForFailover.
    DNS requests against sameness groups without this field set will now error as intended.
  • error running consul server in 1.18.0: failed to configure SCADA provider user's home directory path: $HOME is not defined [GH-20926]
  • server: fix Ent snapshot restore on CE when CE downgrade is enabled [GH-20977]
  • xds: Make TCP external service registered with terminating gateway reachable from peered cluster [GH-19881]

v1.18.1

Compare Source

Enterprise LTS: Consul Enterprise 1.18 is a Long-Term Support (LTS) release.

BREAKING CHANGES:

  • ui: Adds a "Link to HCP Consul Central" modal with integration to side-nav and link to HCP banner. There will be an option to disable the Link to HCP banner from the UI in a follow-up release. [GH-20474]

SECURITY:

IMPROVEMENTS:

  • api: Randomize the returned server list for the WatchServers gRPC endpoint. [GH-20866]
  • partitions: (Enterprise only) Allow disabling of Gossip per Partition [GH-20669]
  • snapshot agent: (Enterprise only) Add support for multiple snapshot destinations using the backup_destinations config file object.
  • xds: Improved the performance of xDS server side load balancing. Its slightly improved in Consul CE with drastic CPU usage reductions in Consul Enterprise. [GH-20672]

BUG FIXES:

  • audit-logs: (Enterprise Only) Fixes non ASCII characters in audit logs because of gzip. [GH-20345]
  • connect: Fix issue where Consul-dataplane xDS sessions would not utilize the streaming backend for wan-federated queries. [GH-20868]
  • connect: Fix potential goroutine leak in xDS stream handling. [GH-20866]
  • connect: Fix xDS deadlock that could result in proxies being unable to start. [GH-20867]
  • ingress-gateway: (Enterprise Only) Fix a bug where on update, Ingress Gateways lost all upstreams for listeners with wildcard services in a different namespace.

v1.18.0

Compare Source

BREAKING CHANGES:

  • config-entries: Allow disabling request and idle timeouts with negative values in service router and service resolver config entries. [GH-19992]
  • telemetry: Adds fix to always use the value of telemetry.disable_hostname when determining whether to prefix gauge-type metrics with the hostname of the Consul agent. Previously, if only the default metric sink was enabled, this configuration was ignored and always treated as true, even though its default value is false. [GH-20312]

SECURITY:

FEATURES:

  • acl: add policy bindtype to binding rules. [GH-19499]
  • agent: Introduces a new agent config default_intention_policy to decouple the default intention behavior from ACLs [GH-20544]
  • agent: (Enterprise Only) Add fault injection filter support for Consul Service Mesh
  • cloud: Adds new API/CLI to initiate and manage linking a Consul cluster to HCP Consul Central [GH-20312]
  • dns: adds experimental support for a refactored DNS server that is v1 and v2 Catalog compatible.
    Use v2dns in the experiments agent config to enable.
    It will automatically be enabled when using the resource-apis (Catalog v2) experiment.
    The new DNS implementation will be the default in Consul 1.19.
    See the Consul 1.18.x Release Notes for deprecated DNS features. [GH-20643]
  • ui: Added a banner to let users link their clusters to HCP [GH-20275]
  • ui: Adds a redirect and warning message around unavailable UI with V2 enabled [GH-20359]
  • ui: adds V2CatalogEnabled to config that is passed to the ui [GH-20353]
  • v2: prevent use of the v2 experiments in secondary datacenters for now [GH-20299]

IMPROVEMENTS:

  • cloud: unconditionally add Access-Control-Expose-Headers HTTP header [GH-20220]
  • connect: Replace usage of deprecated Envoy field envoy.config.core.v3.HeaderValueOption.append. [GH-20078]
  • connect: Replace usage of deprecated Envoy fields envoy.config.route.v3.HeaderMatcher.safe_regex_match and envoy.type.matcher.v3.RegexMatcher.google_re2. [GH-20013]
  • docs: add Link API documentation [GH-20308]
  • resource: lowercase names enforced for v2 resources only. [GH-19218]

BUG FIXES:

  • dns: SERVFAIL when resolving not found PTR records. [GH-20679]
  • raft: Fix panic during downgrade from enterprise to oss. [GH-19311]
  • server: Ensure controllers are automatically restarted on internal stream errors. [GH-20642]
  • server: Ensure internal streams are properly terminated on snapshot restore. [GH-20642]
  • snapshot-agent: (Enterprise only) Fix a bug with static AWS credentials where one of the key id or secret key is provided via config file and the other is provided via an environment variable.

v1.17.3

Compare Source

SECURITY:

FEATURES:

  • cli: Adds new command exported-services to list all services exported and their consumers. Refer to the CLI docs for more information. [GH-20331]

IMPROVEMENTS:

  • ProxyCfg: avoid setting a watch on Internal.ServiceDump when mesh gateway is not used. [GH-20168]
  • ProxyCfg: only return the nodes list when querying the Internal.ServiceDump watch from proxycfg [GH-20168]
  • Upgrade to use Go 1.21.7. [GH-20545]
  • api: add a new api(/v1/exported-services) to list all the exported service and their consumers. [GH-20015]
  • connect: Add CaseInsensitive flag to service-routers that allows paths and path prefixes to ignore URL upper and lower casing. [GH-19647]

BUG FIXES:

  • audit-logs: (Enterprise Only) Fixes non ASCII characters in audit logs because of gzip. [GH-20345]
  • connect: Fix issue where re-persisting existing proxy-defaults using http protocol fails with a protocol-mismatch error. [GH-20481]
  • connect: Fix regression with SAN matching on terminating gateways GH-20360 [GH-20417]
  • connect: Remove code coupling where the xDS capacity controller could negatively affect raft autopilot performance. [GH-20511]
  • logging: add /api prefix to v2 resource endpoint logs [GH-20352]
  • mesh: Fix bug where envoy extensions could not be configured with "permissive" mTLS mode. Note that envoy extensions currently do not apply to non-mTLS traffic in permissive mode. [GH-20406]

v1.17.2

Compare Source

KNOWN ISSUES:

  • connect: Consul versions 1.17.2 and 1.16.5 perform excessively strict TLS SAN verification on terminating gateways, which prevents connections outside of the mesh to upstream services. Terminating gateway users are advised to avoid deploying these Consul versions. A fix will be present in a future release of Consul 1.17.3 and 1.16.6. [GH-20360]

SECURITY:

  • Upgrade OpenShift container images to use ubi9-minimal:9.3 as the base image. [GH-20014]

IMPROVEMENTS:

  • connect: Remove usage of deprecated Envoy field match_subject_alt_names in favor of match_typed_subject_alt_names. [GH-19954]
  • connect: replace usage of deprecated Envoy field envoy.config.router.v3.WeightedCluster.total_weight. [GH-20011]
  • xds: Replace usage of deprecated Envoy field envoy.config.cluster.v3.Cluster.http_protocol_options [GH-20010]
  • xds: remove usages of deprecated Envoy fields: envoy.config.cluster.v3.Cluster.http2_protocol_options, envoy.config.bootstrap.v3.Admin.access_log_path [GH-19940]
  • xds: replace usage of deprecated Envoy field envoy.extensions.filters.http.lua.v3.Lua.inline_code [GH-20012]

DEPRECATIONS:

  • cli: Deprecate the -admin-access-log-path flag from consul connect envoy command in favor of: -admin-access-log-config. [GH-19943]

BUG FIXES:

  • prepared-query: (Enterprise-only) Fix issue where sameness-group failover targets to peers would attempt to query data from the default partition, rather than the sameness-group's partition always.
  • ui: update token list on Role details page to show only linked tokens [GH-19912]

v1.17.1

Compare Source

SECURITY:

  • Update github.com/golang-jwt/jwt/v4 to v4.5.0 to address PRISMA-2022-0270. [GH-19705]
  • Upgrade to use Go 1.20.12. This resolves CVEs
    CVE-2023-45283: (path/filepath) recognize ??\ as a Root Local Device path prefix (Windows)
    CVE-2023-45284: recognize device names with trailing spaces and superscripts (Windows)
    CVE-2023-39326: (net/http) limit chunked data overhead
    CVE-2023-45285: (cmd/go) go get may unexpectedly fallback to insecure git [GH-19840]
  • connect: update supported envoy versions to 1.24.12, 1.25.11, 1.26.6, 1.27.2 to address CVE-2023-44487 [GH-19274]

FEATURES:

  • acl: Adds nomad client templated policy [GH-19827]
  • cli: Adds new subcommand peering exported-services to list services exported to a peer . Refer to the CLI docs for more information. [GH-19821]

IMPROVEMENTS:

  • mesh: parse the proxy-defaults protocol when write the config-entry to avoid parsing it when compiling the discovery chain. [GH-19829]
  • wan-federation: use a hash to diff config entries when replicating in the secondary DC to avoid unnecessary writes.. [GH-19795]
  • Replaces UI Side Nav with Helios Design System Side Nav. Adds dc/partition/namespace searching in Side Nav. [GH-19342]
  • acl: add api-gateway templated policy [GH-19728]
  • acl: add templated policy descriptions [GH-19735]
  • api: Add support for listing ACL tokens by service name when using templated policies. [GH-19666]
  • cli: stop simultaneous usage of -templated-policy and -templated-policy-file when creating a role or token. [GH-19389]
  • cloud: push additional server TLS metadata to HCP [GH-19682]
  • connect: Default stats_flush_interval to 60 seconds when using the Consul Telemetry Collector, unless custom stats sink are present or an explicit flush interval is configured. [GH-19663]
  • metrics: increment consul.client.rpc.failed if RPC fails because no servers are accessible [GH-19721]
  • metrics: modify consul.client.rpc metric to exclude internal retries for consistency with consul.client.rpc.exceeded and consul.client.rpc.failed [GH-19721]
  • ui: move nspace and partitions requests into their selector menus [GH-19594]

BUG FIXES:

  • CLI: fix a panic when deleting a non existing policy by name. [GH-19679]
  • Mesh Gateways: Fix a bug where replicated and peered mesh gateways with hostname-based WAN addresses fail to initialize. [GH-19268]
  • ca: Fix bug with Vault CA provider where renewing a retracted token would cause retries in a tight loop, degrading performance. [GH-19285]
  • ca: Fix bug with Vault CA provider where token renewal goroutines could leak if CA failed to initialize. [GH-19285]
  • connect: Solves an issue where two upstream services with the same name in different namespaces were not getting routed to correctly by API Gateways. [GH-19860]
  • federation: (Enterprise Only) Fixed an issue where namespace reconciliation could result into the secondary having dangling instances of namespaces marked for deletion
  • ui: clear peer on home logo link [GH-19549]
  • ui: fix being able to view peered services from non-default namnespaces [GH-19586]
  • ui: stop manually reconciling services if peering is enabled [GH-19907]
  • wan-federation: Fix a bug where servers wan-federated through mesh-gateways could crash due to overlapping LAN IP addresses. [GH-19503]
  • xds: Add configurable xds_fetch_timeout_ms option to proxy registrations that allows users to prevent endpoints from dropping when they have proxies with a large number of upstreams. [GH-19871]
  • xds: ensure child resources are re-sent to Envoy when the parent is updated even if the child already has pending updates. [GH-19866]

v1.17.0

Compare Source

BREAKING CHANGES:

  • api: RaftLeaderTransfer now requires an id string. An empty string can be specified to keep the old behavior. [GH-17107]
  • audit-logging: (Enterprise only) allowing timestamp based filename only on rotation. initially the filename will be just file.json [GH-18668]

DEPRECATIONS:

  • cli: Deprecate the -admin-access-log-path flag from consul connect envoy command in favor of: -admin-access-log-config. [GH-15946]

SECURITY:

FEATURE PREVIEW: Catalog v2

This release provides the ability to preview Consul's v2 Catalog and Resource API if enabled. The new model supports
multi-port application deployments with only a single Envoy proxy. Note that the v1 and v2 catalogs are not cross
compatible, and not all Consul features are available within this v2 feature preview. See the v2 Catalog and Resource
API documentation
for more information. The v2 Catalog and
Resources API should be considered a feature preview within this release and should not be used in production
environments.

Limitations

  • The v2 catalog API feature preview does not support connections with client agents. As a result, it is only available for Kubernetes deployments, which use Consul dataplanes instead of client agents.
  • The v1 and v2 catalog APIs cannot run concurrently.
  • The Consul UI does not support multi-port services or the v2 catalog API in this release.
  • HCP Consul does not support multi-port services or the v2 catalog API in this release.

Significant Pull Requests

FEATURES:

  • Support custom watches on the Consul Controller framework. [GH-18439]
  • Windows: support consul connect envoy command on Windows [GH-17694]
  • acl: Add BindRule support for templated policies. Add new BindType: templated-policy and BindVar field for templated policy variables. [GH-18719]
  • acl: Add new acl.tokens.dns config field which specifies the token used implicitly during dns checks. [GH-17936]
  • acl: Added ACL Templated policies to simplify getting the right ACL token. [GH-18708]
  • acl: Adds a new ACL rule for workload identities [GH-18769]
  • acl: Adds workload identity templated policy [GH-19077]
  • api-gateway: Add support for response header modifiers on http-route configuration entry [GH-18646]
  • api-gateway: add retry and timeout filters [GH-18324]
  • cli: Add bind-var flag to consul acl binding-rule for templated policy variables. [GH-18719]
  • cli: Add consul acl templated-policy commands to read, list and preview templated policies. [GH-18816]
  • config-entry(api-gateway): (Enterprise only) Add GatewayPolicy to APIGateway Config Entry listeners
  • config-entry(api-gateway): (Enterprise only) Add JWTFilter to HTTPRoute Filters
  • dataplane: Allow getting bootstrap parameters when using V2 APIs [GH-18504]
  • gateway: (Enterprise only) Add JWT authentication and authorization to APIGateway Listeners and HTTPRoutes.
  • mesh: (Enterprise only) Adds rate limiting config to service-defaults [GH-18583]
  • xds: Add a built-in Envoy extension that appends OpenTelemetry Access Logging (otel-access-logging) to the HTTP Connection Manager filter. [GH-18336]
  • xds: Add support for patching outbound listeners to the built-in Envoy External Authorization extension. [GH-18336]

IMPROVEMENTS:

  • raft: upgrade raft-wal library version to 0.4.1. [GH-19314]
  • xds: Use downstream protocol when connecting to local app [GH-18573]
  • Windows: Integration tests for Consul Windows VMs [GH-18007]
  • acl: Use templated policy to generate synthetic policies for tokens/roles with node and/or service identities [GH-18813]
  • api: added CheckRegisterOpts to Agent API [GH-18943]
  • api: added Token field to ServiceRegisterOpts type in Agent API [GH-18983]
  • ca: Vault CA provider config no longer requires root_pki_path for secondary datacenters [GH-17831]
  • cli: Added -templated-policy, -templated-policy-file, -replace-templated-policy, -append-templated-policy, -replace-templated-policy-file, -append-templated-policy-file and -var flags for creating or updating tokens/roles. [GH-18708]
  • config: Add new tls.defaults.verify_server_hostname configuration option. This specifies the default value for any interfaces that support the verify_server_hostname option. [GH-17155]
  • connect: update supported envoy versions to 1.24.10, 1.25.9, 1.26.4, 1.27.0 [GH-18300]
  • ui: Use Community verbiage [GH-18560]

BUG FIXES:

  • api: add custom marshal/unmarshal for ServiceResolverConfigEntry.RequestTimeout so config entries that set this field can be read using the API. [GH-19031]
  • ca: ensure Vault CA provider respects Vault Enterprise namespace configuration. [GH-19095]
  • catalog api: fixes a bug with catalog api where filter query parameter was not working correctly for the /v1/catalog/services endpoint [GH-18322]
  • connect: (Enterprise only) Fix bug where incorrect service-defaults entries were fetched to determine an upstream's protocol whenever the upstream did not explicitly define the namespace / partition. When this bug occurs, upstreams would use the protocol from a service-default entry in the default namespace / partition, rather than their own namespace / partition.
  • connect: Fix bug where uncleanly closed xDS connections would influence connection balancing for too long and prevent envoy instances from starting. Two new configuration fields
    performance.grpc_keepalive_timeout and performance.grpc_keepalive_interval now exist to allow for configuration on how often these dead connections will be cleaned up. [GH-19339]
  • dev-mode: Fix dev mode has new line in responses. Now new line is added only when url has pretty query parameter. [GH-18367]
  • dns: (Enterprise only) Fix bug where sameness group queries did not correctly inherit the agent's partition.
  • docs: fix list of telemetry metrics [GH-17593]
  • gateways: Fix a bug where a service in a peered datacenter could not access an external node service through a terminating gateway [GH-18959]
  • server: (Enterprise Only) Fixed an issue where snake case keys were rejected when configuring the control-plane-request-limit config entry
  • telemetry: emit consul version metric on a regular interval. [GH-6876]
  • tlsutil: Default setting of ServerName field in outgoing TLS configuration for checks now handled by crypto/tls. [GH-17481]

v1.16.6

Compare Source

SECURITY:

IMPROVEMENTS:

  • ProxyCfg: avoid setting a watch on Internal.ServiceDump when mesh gateway is not used. [GH-20168]
  • ProxyCfg: only return the nodes list when querying the Internal.ServiceDump watch from proxycfg [GH-20168]
  • Upgrade to use Go 1.21.7. [GH-20545]

BUG FIXES:

  • audit-logs: (Enterprise Only) Fixes non ASCII characters in audit logs because of gzip. [GH-20345]
  • connect: Fix issue where re-persisting existing proxy-defaults using http protocol fails with a protocol-mismatch error. [GH-20481]
  • connect: Fix regression with SAN matching on terminating gateways GH-20360 [GH-20417]
  • connect: Remove code coupling where the xDS capacity controller could negatively affect raft autopilot performance. [GH-20511]
  • mesh: Fix bug where envoy extensions could not be configured with "permissive" mTLS mode. Note that envoy extensions currently do not apply to non-mTLS traffic in permissive mode. [GH-20406]

v1.16.5

Compare Source

KNOWN ISSUES:

  • connect: Consul versions 1.17.2 and 1.16.5 perform excessively strict TLS SAN verification on terminating gateways, which prevents connections outside of the mesh to upstream services. Terminating gateway users are advised to avoid deploying these Consul versions. A fix will be present in a future release of Consul 1.17.3 and 1.16.6 [GH-20360].

SECURITY:

  • Update RSA key generation to use a key size of at least 2048 bits. [GH-20112]
  • Upgrade OpenShift container images to use ubi9-minimal:9.3 as the base image. [GH-20014]

IMPROVEMENTS:

  • Upgrade to use Go 1.21.6. [GH-20062]
  • connect: Remove usage of deprecated Envoy field match_subject_alt_names in favor of match_typed_subject_alt_names. [GH-19954]
  • connect: replace usage of deprecated Envoy field envoy.config.router.v3.WeightedCluster.total_weight. [GH-20011]
  • xds: Replace usage of deprecated Envoy field envoy.config.cluster.v3.Cluster.http_protocol_options [GH-20010]
  • xds: remove usages of deprecated Envoy fields: envoy.config.cluster.v3.Cluster.http2_protocol_options, envoy.config.bootstrap.v3.Admin.access_log_path [GH-19940]
  • xds: replace usage of deprecated Envoy field envoy.extensions.filters.http.lua.v3.Lua.inline_code [GH-20012]

BUG FIXES:

  • prepared-query: (Enterprise-only) Fix issue where sameness-group failover targets to peers would attempt to query data from the default partition, rather than the sameness-group's partition always.
  • ui: update token list on Role details page to show only linked tokens [GH-19912]

v1.16.4

Compare Source

SECURITY:

  • Update github.com/golang-jwt/jwt/v4 to v4.5.0 to address PRISMA-2022-0270. [GH-19705]
  • Upgrade to use Go 1.20.12. This resolves CVEs
    CVE-2023-45283: (path/filepath) recognize ??\ as a Root Local Device path prefix (Windows)
    CVE-2023-45284: recognize device names with trailing spaces and superscripts (Windows)
    CVE-2023-39326: (net/http) limit chunked data overhead
    CVE-2023-45285: (cmd/go) go get may unexpectedly fallback to insecure git [GH-19840]

IMPROVEMENTS:

  • mesh: parse the proxy-defaults protocol when write the config-entry to avoid parsing it when compiling the discovery chain. [GH-19829]
  • wan-federation: use a hash to diff config entries when replicating in the secondary DC to avoid unnecessary writes.. [GH-19795]
  • cli: Adds cli support for checking TCP connection for ports. If -ports flag is not given, it will check for
    default ports of consul listed here - https://developer.hashicorp.com/consul/docs/install/ports [GH-18329]
  • cloud: push additional server TLS metadata to HCP [GH-19682]
  • connect: Default stats_flush_interval to 60 seconds when using the Consul Telemetry Collector, unless custom stats sink are present or an explicit flush interval is configured. [GH-19663]
  • metrics: increment consul.client.rpc.failed if RPC fails because no servers are accessible [GH-19721]
  • metrics: modify consul.client.rpc metric to exclude internal retries for consistency with consul.client.rpc.exceeded and consul.client.rpc.failed [GH-19721]

BUG FIXES:

  • CLI: fix a panic when deleting a non existing policy by name. [GH-19679]
  • connect: Solves an issue where two upstream services with the same name in different namespaces were not getting routed to correctly by API Gateways. [GH-19860]
  • federation: (Enterprise Only) Fixed an issue where namespace reconciliation could result into the secondary having dangling instances of namespaces marked for deletion
  • ui: only show hcp link if url is present [GH-19443]
  • wan-federation: Fix a bug where servers wan-federated through mesh-gateways could crash due to overlapping LAN IP addresses. [GH-19503]
  • xds: Add configurable xds_fetch_timeout_ms option to proxy registrations that allows users to prevent endpoints from dropping when they have proxies with a large number of upstreams. [GH-19871]
  • xds: ensure child resources are re-sent to Envoy when the parent is updated even if the child already has pending updates. [GH-19866]

v1.16.3

Compare Source

SECURITY:

BUG FIXES:

  • Mesh Gateways: Fix a bug where replicated and peered mesh gateways with hostname-based WAN addresses fail to initialize. [GH-19268]
  • api-gateway: fix matching for different hostnames on the same listener [GH-19120]
  • api: add custom marshal/unmarshal for ServiceResolverConfigEntry.RequestTimeout so config entries that set this field can be read using the API. [GH-19031]
  • ca: Fix bug with Vault CA provider where renewing a retracted token would cause retries in a tight loop, degrading performance. [GH-19285]
  • ca: Fix bug with Vault CA provider where token renewal goroutines could leak if CA failed to initialize. [GH-19285]
  • ca: ensure Vault CA provider respects Vault Enterprise namespace configuration. [GH-19095]
  • catalog api: fixes a bug with catalog api where filter query parameter was not working correctly for the /v1/catalog/services endpoint [GH-18322]
  • connect: Fix bug where uncleanly closed xDS connections would influence connection balancing for too long and prevent envoy instances from starting. Two new configuration fields
    performance.grpc_keepalive_timeout and performance.grpc_keepalive_interval now exist to allow for configuration on how often these dead connections will be cleaned up. [GH-19339]
  • dns: (Enterprise only) Fix bug where sameness group queries did not correctly inherit the agent's partition.
  • gateways: Fix a bug where a service in a peered datacenter could not access an external node service through a terminating gateway [GH-18959]
  • server: (Enterprise Only) Fixed an issue where snake case keys were rejected when configuring the control-plane-request-limit config entry

v1.16.2

Compare Source

SECURITY:

IMPROVEMENTS:

  • Adds flag -append-filename (which works on values version, dc, node and status) to consul snapshot save command.
    Adding the flag -append-filename version,dc,node,status will add consul version, consul datacenter, node name and leader/follower
    (status) in the file name given in the snapshot save command before the file extension. [GH-18625]
  • Reduce the frequency of metric exports from Consul to HCP from every 10s to every 1m [GH-18584]
  • api: Add support for listing ACL tokens by service name. [GH-18667]
  • checks: It is now possible to configure agent TCP checks to use TLS with
    optional server SNI and mutual authentication. To use TLS with a TCP check, the
    check must enable the tcp_use_tls boolean. By default the agent will use the
    TLS configuration in the tls.default stanza. [GH-18381]
  • command: Adds -since flag in consul debug command which internally calls hcdiag for debug information in the past. [GH-18797]
  • log: Currently consul logs files like this consul-{timestamp}.log. This change makes sure that there is always
    consul.log file wi

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team July 20, 2023 07:37
@renovate
Copy link
Contributor Author

renovate bot commented Jul 20, 2023

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 7 times, most recently from 4a3e83d to b30c242 Compare July 24, 2023 03:06
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 4 times, most recently from 59c4cc9 to e336c1b Compare August 8, 2023 16:15
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.16.0 chore(deps): update hashicorp/consul docker tag to v1.16.1 Aug 8, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 2 times, most recently from deb46ba to 912d508 Compare September 5, 2023 06:52
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 3 times, most recently from fd8aa94 to d97884e Compare September 20, 2023 00:14
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.16.1 chore(deps): update hashicorp/consul docker tag to v1.16.2 Sep 20, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from d97884e to 03606c9 Compare September 25, 2023 04:04
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from 03606c9 to b24b891 Compare October 31, 2023 19:51
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.16.2 chore(deps): update hashicorp/consul docker tag to v1.16.3 Oct 31, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 2 times, most recently from 32ad394 to 367cafd Compare November 3, 2023 19:18
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.16.3 chore(deps): update hashicorp/consul docker tag to v1.17.0 Nov 3, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from 367cafd to 186e118 Compare November 6, 2023 04:48
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from 186e118 to 01cdf46 Compare November 21, 2023 09:35
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from 01cdf46 to 2431514 Compare December 15, 2023 00:16
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 3 times, most recently from e6e5402 to acc9df5 Compare May 17, 2024 18:41
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.18.1 chore(deps): update hashicorp/consul docker tag to v1.18.2 May 17, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from acc9df5 to 456040f Compare May 20, 2024 07:59
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 2 times, most recently from 6550155 to 92cfa05 Compare June 3, 2024 02:16
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from 92cfa05 to ade8051 Compare June 12, 2024 19:19
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.18.2 chore(deps): update hashicorp/consul docker tag to v1.19.0 Jun 12, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 3 times, most recently from 3ab457c to ca1a4ba Compare July 8, 2024 04:18
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from ca1a4ba to a88c4de Compare July 12, 2024 00:23
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.19.0 chore(deps): update hashicorp/consul docker tag to v1.19.1 Jul 12, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from a88c4de to f938058 Compare August 23, 2024 23:15
@renovate renovate bot requested a review from a team as a code owner August 23, 2024 23:15
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 2 times, most recently from b7b87c7 to 9ef120e Compare August 27, 2024 21:33
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.19.1 chore(deps): update hashicorp/consul docker tag to v1.19.2 Aug 27, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 3 times, most recently from ad9afd2 to 2db1de3 Compare September 16, 2024 03:02
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch 4 times, most recently from 111c3c1 to de8797a Compare October 15, 2024 03:55
@renovate renovate bot changed the title chore(deps): update hashicorp/consul docker tag to v1.19.2 chore(deps): update hashicorp/consul docker tag to v1.20.0 Oct 15, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from de8797a to a1a9dd5 Compare October 17, 2024 22:57
@renovate renovate bot force-pushed the renovate/hashicorp-consul-1.x branch from a1a9dd5 to 87d8c2e Compare October 21, 2024 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants