Charmed MySQL K8s
- Canonical
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 8.0/stable | 180 | 02 Sep 2024 | |
| 8.0/stable | 181 | 02 Sep 2024 | |
| 8.0/candidate | 211 | 11 Dec 2024 | |
| 8.0/candidate | 210 | 11 Dec 2024 | |
| 8.0/beta | 211 | 09 Dec 2024 | |
| 8.0/beta | 210 | 09 Dec 2024 | |
| 8.0/edge | 211 | 09 Dec 2024 | |
| 8.0/edge | 210 | 09 Dec 2024 |
juju deploy mysql-k8s --channel 8.0/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Profiles
Charmed MySQL K8s resource utilization depends on the chosen profile:
juju deploy mysql-k8s --trust --config profile=testing
Profile values
| Value | Description | Tech details |
|---|---|---|
production(default) |
Maximum performance | ~75% of ‘Allocatable memory’ granted for MySQL max_connections=RAM/12MiB (max safe value) |
testing |
Minimal resource usage | innodb_buffer_pool_size = 20MB innodb_buffer_pool_chunk_size=1MB group_replication_message_cache_size=128MB max_connections=100 performance-schema-instrument=‘memory/%=OFF’ |
Config change
Note: Pre-deployed application profile change is planned but currently is NOT supported.
To change the profile, use juju config (see all charm configs):
juju deploy mysql-k8s --trust --config profile=testing && \
juju config mysql-k8s profile=production
Juju Constraints
Juju constraints allows RAM/CPU limits for Kubernetes pods:
juju deploy mysql-k8s --trust --constraints cores=8 mem=16G
Juju constraints can be used together with charm profile:
juju deploy mysql-k8s --trust --constraints cores=8 mem=16G --config profile=testing