mysql-router-k8s

MySQL Router K8s

Channel Revision Published Runs on
8.0/stable 748 23 Jun 2025
Ubuntu 22.04
8.0/stable 747 23 Jun 2025
Ubuntu 22.04
8.0/candidate 748 16 Jun 2025
Ubuntu 22.04
8.0/candidate 747 16 Jun 2025
Ubuntu 22.04
8.0/beta 748 23 Jun 2025
Ubuntu 22.04
8.0/beta 747 23 Jun 2025
Ubuntu 22.04
8.0/edge 838 02 Oct 2025
Ubuntu 22.04
8.0/edge 837 02 Oct 2025
Ubuntu 22.04
8.0/edge 836 02 Oct 2025
Ubuntu 22.04
juju deploy mysql-router-k8s --channel 8.0/edge
Show information

Platform:

Learn about actions >

  • 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 to all, this action will refresh the next unit.

    If pause-after-unit-refresh is set to first, 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 to none, this action will have no effect unless it is called with check-health-of-refreshed-units as false.

    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 unhealthy

      Warning: 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 the force-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.