
Charmed MySQL Router
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 256 | 16 Oct 2024 | |
latest/edge | 255 | 16 Oct 2024 | |
latest/edge | 254 | 16 Oct 2024 | |
latest/edge | 253 | 16 Oct 2024 | |
latest/edge | 201 | 19 Jun 2024 | |
latest/edge | 108 | 12 Sep 2023 | |
latest/edge | 62 | 10 Feb 2023 | |
8.0/stable | 257 | 17 Oct 2024 | |
dpe/candidate | 356 | 31 Mar 2025 | |
dpe/candidate | 355 | 31 Mar 2025 | |
dpe/candidate | 354 | 31 Mar 2025 | |
dpe/beta | 356 | 24 Mar 2025 | |
dpe/beta | 355 | 24 Mar 2025 | |
dpe/beta | 354 | 24 Mar 2025 | |
dpe/edge | 1054 | 03 Sep 2025 | |
dpe/edge | 1053 | 03 Sep 2025 | |
dpe/edge | 1052 | 03 Sep 2025 | |
dpe/edge | 362 | 31 Mar 2025 | |
8.0.19/stable | 26 | 05 May 2022 | |
8.0.19/edge | 26 | 05 May 2022 | |
8.0.19/edge | 15 | 26 Apr 2022 |
juju deploy mysql-router --channel dpe/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
force-refresh-start
Potential of data loss and downtime
Force refresh of first unit
Must run with at least one of the parameters
=false
- Params
-
check-compatibility boolean
Potential of data loss and downtime
If
false
, force refresh if new version of Router and/or charm is not compatible with previous version -
check-workload-container boolean
Potential of data loss and downtime during and after refresh
If
false
, allow refresh to Router container version that has not been validated to work with the charm revision -
run-pre-refresh-checks boolean
Potential of data loss and downtime
If
false
, force refresh if app is unhealthy or not ready to refresh (and unit status shows "Pre-refresh check failed")
-
pre-refresh-check
Check if charm is ready to refresh
-
resume-refresh
Refresh next unit(s) (after you have manually verified that refreshed units are healthy)
If the
pause-after-unit-refresh
config is set toall
, this action will refresh the next unit.If
pause-after-unit-refresh
is set tofirst
, this action will refresh all remaining units. Exception: if automatic health checks fail after a unit has refreshed, the refresh will pause.If
pause-after-unit-refresh
is set tonone
, this action will have no effect unless it is called withcheck-health-of-refreshed-units
asfalse
.- Params
-
check-health-of-refreshed-units boolean
Potential of data loss and downtime
If
false
, force refresh (of next unit) if 1 or more refreshed units are unhealthyWarning: if first unit to refresh is unhealthy, consider running
force-refresh-start
action on that unit instead of using this parameter. If first unit to refresh is unhealthy because compatibility checks, pre-refresh checks, or workload container checks are failing, this parameter is more destructive than theforce-refresh-start
action.
-
set-tls-private-key
Set the private key, which will be used for certificate signing requests (CSR). Run for each unit separately.
- Params
-
internal-key string
The content of private key for internal communications with clients. Content will be auto-generated if this option is not specified.