Bump consul to v1.14
What does this MR do?
Bump consul from 1.12.5 to 1.14.7.
This bump follows the consul upgrade path, which allows jumping 2 minor versions at a time.
Consul Upgrade Docs: https://developer.hashicorp.com/consul/docs/upgrading/instructions#general-upgrade-path
Closes: #7798 (closed)
Changelog: changed
Bump consul by two major versions according to the consul docs:
Each upgrade should jump at most 2 major versions, except where dedicated instructions are provided for a larger jump between specific versions.
Changelog:
Important Consul changes
Service mesh deployments without the HTTPS port enabled on Consul agents
Omnibus handling Consul TLS configuration: https://gitlab.com/gitlab-org/omnibus-gitlab/-/blob/master/files/gitlab-cookbooks/consul/libraries/consul_helper.rb#L40-L59
Current Estimation: No changes to be made on omnibus side as Omnibus configures either:
- both
tls.defaults
andports { https: x}
(enabling HTTPS and gRPC TLS) - neither
tls.defaults
andports { https: x}
(disabling HTTPS and gRPC TLS)
Related issues
Closes #7798 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
Latest Merge Result pipeline is green. -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
-
The manual Trigger:ee-package
jobs have a green pipeline running against latest commit. -
If config/software
orconfig/patches
directories are changed, make sure thebuild-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, then the Trigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline must succeed. -
If CI configuration is changed, the branch must be pushed todev.gitlab.org
to confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. -
Tests added. -
Integration tests added to GitLab QA. -
Equivalent MR/issue for the GitLab Chart opened. -
Validate potential values for new configuration settings. Formats such as integer10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.