We're really excited to announce the availability of Consul 1.7.0. Consul is a multi-cloud service networking platform to connect and secure services across any runtime platform and public or private cloud.
This release includes the following features:
Release 1.7.0 is available for beta now, with general availability to follow. Please review the v1.7.0 changelog for a detailed list of changes. The binaries can be downloaded here.
Note: This is a Consul Enterprise feature
Traditionally, Consul has utilized a single, global scope for resources within an environment. All resources share this single scope for naming. This creates challenges in large scale, multi-user environments as teams must ensure distinct services utilize either unique names or tags and service metadata to differentiate themselves from services belonging to another team. This introduces additional operational overhead to ensure no conflicts exist and can increase the risk of misconfigurations if this process is not automated. In addition, administrative privileges are centralized at the global level, which places additional burden on operators to manage simple, day-to-day administrative tasks required by individual teams.
Namespaces allow a Consul environment to be divided into one or more logical environments that provide resource separation and allow the re-use of service names or K/V prefixes across namespaces—removing the requirement to coordinate resource names between teams.
In addition, operators may sub-delegate administrative privileges for a given namespace to individual teams, enabling self-service for ACLs, tokens, policies, service registrations, K/V prefixes, and central configurations (a new feature for defining site-wide or service-specific Connect proxy configurations via the API) within the respective namespace.
With this feature, users will be able to:
Note: This is a Consul Enterprise feature
Consul Enterprise automatically saves and restores the state of Consul servers for disaster recovery. The snapshot feature enables point-in-time backups of the K/V store, ACLs, service catalogs, plus prepared queries, automated backup files rotation, and the ability to store the backup file in a cloud storage service like Amazon S3 or Azure Storage. With this release, we are adding the capability to store the backup in Google Cloud Platform (GCP).
Consul provides an internal CA and can also use Vault to provide certificates. With this release, we are adding the ability to use AWS PCA as a CA for Consul.
Thank you to our active community members who have been invaluable by adding new features, reporting bugs, and improving the documentation for Consul in this release!
Please also read this additional blog on the business value of the 1.7.0 release.
To see a live demo of these new features, watch the Consul 1.7 webinar here.
HCP Consul Central’s new observability features were recently used by a customer to help troubleshoot an issue with assistance from HashiCorp engineers.
If you’re attending AWS re:Invent in Las Vegas, Nov. 27 - Dec. 1, visit us for breakout sessions, expert talks, and product demos to learn how to accelerate your adoption of a cloud operating model.
Consul 1.17 enhances unified workflow management, reliability, scale, and security for service networking.