-
Enhancement
-
Resolution: Done
-
Critical
-
None
-
2.10 GA
-
5
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Undefined
-
API CCS Sprint 30 (3Scale), API CCS Sprint 32 (3Scale), API CCS Sprint 33 (3Scale), API CCS Sprint 34 (3Scale), API CCS Sprint 35 (3Scale), API CCS Sprint 36 (3Scale), API CCS Sprint 36 (3Scale), API CCS Sprint 37 (3Scale), API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale)
Current behaviour
The external databases installation guide is very clear when it describes what is the purpose of this part of the configuration at deployment time. However, this is not the only reference to our support for HA deployment options. For template based installations HA is mentioned here, HA support for Redis
Expected behaviour
HA template should be renamed or clarified what exactly HA means in this context. It really means externalised databases and the HA part is entirely at the discretion of the user when they set up those external components.
HA support for Redis should also be clarified for the same reason.
See the section on MySQL, it is more appropriately named.
Notes
There is some context behind this request in the following email thread: https://post-office.corp.redhat.com/archives/sme-apis/2021-August/msg00010.html
- is duplicated by
-
THREESCALE-9601 info on HA templates in 2.13 docs
- Closed
- relates to
-
THREESCALE-9235 [DDF] 3scale templates are no longer supported - HA.
- Closed