mirror of https://github.com/status-im/consul.git
docs: Release notes for Consul 1.12, 1.13 and Consul K8s 0.47.0 (#14352)
* consul 1.12, consul 1.13, and consul-k8s release notes Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
This commit is contained in:
David Yu
GitHub
parent
e64a28516d
commit
b1ba0a89bc
|
|
@ -72,7 +72,7 @@ service mesh.
|
|||
}
|
||||
```
|
||||
1. Issue the `consul services register` command to store the configuration:
|
||||
```shell-sesion
|
||||
```shell-session
|
||||
$ consul services register api-sidecar-proxy.hcl
|
||||
```
|
||||
1. Call the upstream service to invoke the Lambda function. In the following example, the `api` service invokes the `authentication` service at `localhost:2345`:
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ description: >-
|
|||
|
||||
# Consul API Gateway 0.1.0
|
||||
|
||||
## OVerview
|
||||
## Overview
|
||||
|
||||
This is the first general availability (GA) release of Consul API Gateway. It
|
||||
provides controlled access for network traffic from outside a Consul service
|
||||
|
|
|
|||
|
|
@ -0,0 +1,48 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: 0.47.x
|
||||
description: >-
|
||||
Consul on Kubernetes release notes for version 0.47.x
|
||||
---
|
||||
|
||||
# Consul on Kubernetes 0.47.0
|
||||
|
||||
## Release Highlights
|
||||
|
||||
- **Cluster Peering (Beta)**: This release introduces support for Cluster Peering, which allows service connectivity between two independent clusters. Enabling peering will deploy the peering controllers and PeeringAcceptor and PeeringDialer CRDs. The new CRDs are used to establish a peering connection between two clusters. Refer to [Cluster Peering on Kubernetes](/docs/connect/cluster-peering/k8s) for full instructions on using Cluster Peering on Kubernetes.
|
||||
|
||||
- **Envoy Proxy Debugging CLI Commands**: This release introduces new commands to quickly identify proxies and troubleshoot Envoy proxies for sidecars and gateways.
|
||||
* Add `consul-k8s proxy list` command for displaying pods running Envoy managed by Consul.
|
||||
* Add `consul-k8s proxy read podname` command for displaying Envoy configuration for a given pod
|
||||
|
||||
- **Transparent Proxy Egress**: Adds support for destinations on the Service Defaults CRD when using transparent proxy for terminating gateways.
|
||||
|
||||
## Supported Software
|
||||
|
||||
- Consul 1.11.x, Consul 1.12.x and Consul 1.13.1+
|
||||
- Kubernetes 1.19+
|
||||
- Kubernetes 1.24 is not supported at this time.
|
||||
- Kubectl 1.21+
|
||||
- Envoy proxy support is determined by the Consul version deployed. Refer to
|
||||
[Envoy Integration](/docs/connect/proxies/envoy) for details.
|
||||
|
||||
## Upgrading
|
||||
|
||||
For detailed information on upgrading, please refer to the [Upgrades page](/docs/k8s/upgrade)
|
||||
|
||||
## Known Issues
|
||||
|
||||
The following issues are know to exist in the v0.47.0 and v0.47.1 releases
|
||||
|
||||
- Kubernetes 1.24 is not supported because secret-based tokens are no longer autocreated by default for service accounts. Refer to GitHub issue
|
||||
[[GH-1145](https://github.com/hashicorp/consul-k8s/issues/1145)] for
|
||||
details.
|
||||
|
||||
## Changelogs
|
||||
|
||||
The changelogs for this major release version and any maintenance versions are listed below.
|
||||
|
||||
~> **Note:** The following link takes you to the changelogs on the GitHub website.
|
||||
|
||||
- [0.47.0](https://github.com/hashicorp/consul-k8s/releases/tag/v0.47.0)
|
||||
- [0.47.1](https://github.com/hashicorp/consul-k8s/releases/tag/v0.47.1)
|
||||
|
|
@ -24,6 +24,8 @@ description: >-
|
|||
- Drops support for Envoy version 1.13.x.
|
||||
- (Enterprise Only) Consul Enterprise has removed support for temporary licensing. All server agents must have a valid license at startup and client agents must have a license at startup or be able to retrieve one from the servers.
|
||||
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details page](/docs/upgrading/upgrade-specific#consul-1-10-0) and the changelogs.
|
||||
|
||||
## Changelogs
|
||||
|
|
|
|||
|
|
@ -27,6 +27,8 @@ description: >-
|
|||
|
||||
- Drops support for Envoy versions 1.15.x and 1.16.x
|
||||
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details page](/docs/upgrading/upgrade-specific#consul-1-11-0) and the changelogs.
|
||||
|
||||
## Changelogs
|
||||
|
|
|
|||
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: 1.12.x
|
||||
description: >-
|
||||
Consul release notes for version 1.12.x
|
||||
---
|
||||
|
||||
# Consul 1.12.0
|
||||
|
||||
## Release Highlights
|
||||
|
||||
- **AWS IAM Auth Method**: Consul now provides an AWS IAM auth method that allows AWS IAM roles and users to authenticate with Consul to obtain ACL tokens. Refer to [AWS IAM Auth Method](/docs/security/acl/auth-methods/aws-iam) for detailed configuration information.
|
||||
|
||||
- **Per listener TLS Config**: It is now possible to configure TLS differently for each of Consul's listeners, such as HTTPS, gRPC, and the internal multiplexed RPC listener, using the `tls` stanza. Refer to [TLS Configuration Reference](/docs/agent/config/config-files#tls-configuration-reference) for more details.
|
||||
|
||||
- **AWS Lambda**: Adds the ability to invoke AWS Lambdas through terminating gateways, which allows for cross-datacenter communication, transparent proxy, and intentions with Consul Service Mesh. Refer to [AWS Lambda](/docs]/lambda) and [Invoke Lambda Functions](/docs/lambda/invocation) for more details.
|
||||
|
||||
- **Mesh-wide TLS min/max versions and cipher suites:** Using the [Mesh](/docs/connect/config-entries/mesh#tls) Config Entry or CRD, it is now possible to set TLS min/max versions and cipher suites for both inbound and outbound mTLS connections.
|
||||
|
||||
- **Expanded details for ACL Permission Denied errors**: Details are now provided when a permission denied errors surface for RPC calls. Details include the accessor ID of the ACL token, the missing permission, and any namespace or partition that the error occurred on.
|
||||
|
||||
- **ACL token read**: The `consul acl token read -rules` command now includes an `-expanded` option to display detailed info about any policies and rules affecting the token. Refer to [Consul ACL Token read](/commands/acl/token/read) for more details.
|
||||
|
||||
- **Automatically reload agent config when watching agent config file changes**: When using the `auto-reload-config` CLI flag or `auto_reload_config` agent config option, Consul now automatically reloads the [reloadable configuration options](/docs/agent/config#reloadable-configuration) when configuration files change. Refer to [auto_reload_config](/docs/agent/config/cli-flags#_auto_reload_config) for more details.
|
||||
|
||||
|
||||
## What's Changed
|
||||
|
||||
- Removes support for Envoy 1.17.x and Envoy 1.18.x, and adds support for Envoy 1.21.x and Envoy 1.22.x. Refer to the [Envoy Compatibility matrix](/docs/connect/proxies/envoy) for more details.
|
||||
|
||||
- The `disable_compat_1.9` option now defaults to true. Metrics formatted in the style of version 1.9, such as `consul.http...`, can still be enabled by setting disable_compat_1.9 = false. However, these metrics will be removed in 1.13.
|
||||
|
||||
- The `agent_master` ACL token has been renamed to `agent_recovery` ACL token. In addition, the `consul acl set-agent-token master` command has been replaced with `consul acl set-agent-token recovery`. Refer to [ACL Agent Recovery Token](/docs/security/acl/acl-tokens#acl-agent-recovery-token) and [Consul ACL Set Agent Token](/commands/acl/set-agent-token) for more information.
|
||||
|
||||
- If TLS min versions and max versions are not specified, the TLS min/max versions default to the following values. For details on how to configure TLS min and max, refer to the [Mesh TLS config entry](/docs/connect/config-entries/mesh#tls) or CRD documentation.
|
||||
- Incoming connections: TLS 1.2 for min0 version, TLS 1.3 for max version
|
||||
- Outgoing connections: TLS 1.2 for both TLS min and TLS max versions.
|
||||
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details page](/docs/upgrading/upgrade-specific#consul-1-12-0) and the changelogs.
|
||||
|
||||
## Changelogs
|
||||
|
||||
The changelogs for this major release version and any maintenance versions are listed below.
|
||||
|
||||
-> **Note**: These links take you to the changelogs on the GitHub website.
|
||||
|
||||
- [1.12.0](https://github.com/hashicorp/consul/releases/tag/v1.12.0)
|
||||
- [1.12.1](https://github.com/hashicorp/consul/releases/tag/v1.12.1)
|
||||
- [1.12.2](https://github.com/hashicorp/consul/releases/tag/v1.12.2)
|
||||
- [1.12.3](https://github.com/hashicorp/consul/releases/tag/v1.12.3)
|
||||
- [1.12.4](https://github.com/hashicorp/consul/releases/tag/v1.12.4)
|
||||
|
||||
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: 1.13.x
|
||||
description: >-
|
||||
Consul release notes for version 1.13.x
|
||||
---
|
||||
|
||||
# Consul 1.13.0
|
||||
|
||||
## Release Highlights
|
||||
|
||||
- **Cluster Peering (Beta)**: This version adds a new model to federate Consul clusters for both service mesh and traditional service discovery. Cluster peering allows for service interconnectivity with looser coupling than the existing WAN federation. For more information, refer to the [cluster peering](/docs/connect/cluster-peering) documentation.
|
||||
|
||||
- **Transparent proxying through terminating gateways**: This version adds egress traffic control to destinations outside of Consul's catalog, such as APIs on the public internet. Transparent proxies can dial [destinations defined in service-defaults](/docs/connect/config-entries/service-defaults#destination) and have the traffic routed through terminating gateways. For more information, refer to the [terminating gateway](/docs/connect/gateways/terminating-gateway#terminating-gateway-configuration) documentation.
|
||||
|
||||
- **Enables TLS on the Envoy Prometheus endpoint**: The Envoy prometheus endpoint can be enabled when `envoy_prometheus_bind_addr` is set and then secured over TLS using new CLI flags for the `consul connect envoy` command. These commands are: `-prometheus-ca-file`, `-prometheus-ca-path`, `-prometheus-cert-file` and `-prometheus-key-file`. The CA, cert, and key can be provided to Envoy by a Kubernetes mounted volume so that Envoy can watch the files and dynamically reload the certs when the volume is updated.
|
||||
|
||||
- **UDP Health Checks**: Adds the ability to register service discovery health checks that periodically send UDP datagrams to the specified IP/hostname and port. Refer to [UDP checks](/docs/discovery/checks#udp-interval).
|
||||
|
||||
## What's Changed
|
||||
|
||||
- Removes support for Envoy 1.19.x and adds suport for Envoy 1.23. Refer to the [Envoy Compatibility matrix](/docs/connect/proxies/envoy) for more details.
|
||||
|
||||
- The [`disable_compat_19`](/docs/agent/options#telemetry-disable_compat_1.9) telemetry configuration option is now removed. In Consul versions 1.10.x through 1.11.x, the config defaulted to `false`. In version 1.12.x it defaulted to `true`. Before upgrading you should remove this flag from your config if the flag is being used.
|
||||
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details page](/docs/upgrading/upgrade-specific#consul-1-13-0) and the changelogs.
|
||||
|
||||
## Known Issues
|
||||
The following issues are know to exist in the 1.13.0 release:
|
||||
|
||||
- Consul 1.13.1 fixes a compatibility issue when restoring snapshots from pre-1.13.0 versions of Consul. Refer to GitHub issue [[GH-14149](https://github.com/hashicorp/consul/issues/14149)] for more details.
|
||||
- Consul 1.13.0 and Consul 1.13.1 default to requiring TLS for gRPC communication with Envoy proxies when auto-encrypt and auto-config are enabled. In environments where Envoy proxies are not already configured to use TLS for gRPC, upgrading Consul 1.13 will cause Envoy proxies to disconnect from the control plane (Consul agents). A future patch release will default to disabling TLS by default for GRPC communication with Envoy proxies when using Service Mesh and auto-config or auto-encrypt. Refer to GitHub issue [GH-14253](https://github.com/hashicorp/consul/issues/14253) and [Service Mesh deployments using auto-config and auto-enrypt](https://www.consul.io/docs/upgrading/upgrade-specific#service-mesh-deployments-using-auto-encrypt-or-auto-config) for more details.
|
||||
|
||||
|
||||
## Changelogs
|
||||
|
||||
The changelogs for this major release version and any maintenance versions are listed below.
|
||||
|
||||
-> **Note**: These links take you to the changelogs on the GitHub website.
|
||||
|
||||
- [1.13.0](https://github.com/hashicorp/consul/releases/tag/v1.13.0)
|
||||
- [1.13.1](https://github.com/hashicorp/consul/releases/tag/v1.13.1)
|
||||
|
|
@ -1248,6 +1248,14 @@
|
|||
{
|
||||
"title": "Consul",
|
||||
"routes": [
|
||||
{
|
||||
"title": "v1.13.x",
|
||||
"path": "release-notes/consul/v1_13_x"
|
||||
},
|
||||
{
|
||||
"title": "v1.12.x",
|
||||
"path": "release-notes/consul/v1_12_x"
|
||||
},
|
||||
{
|
||||
"title": "v1.11.x",
|
||||
"path": "release-notes/consul/v1_11_x"
|
||||
|
|
@ -1262,6 +1270,15 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "Consul K8s",
|
||||
"routes": [
|
||||
{
|
||||
"title": "v0.47.x",
|
||||
"path": "release-notes/consul-k8s/v0_47_x"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"title": "Consul API Gateway",
|
||||
"routes": [
|
||||
|
|
|
|||
Loading…
Reference in New Issue