You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This chart bootstraps a [MySQL](https://github.com/bitnami/containers/tree/main/bitnami/mysql) replication cluster deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
20
+
This chart bootstraps a [MySQL](https://github.com/drycc/containers/tree/main/drycc/mysql) replication cluster deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
21
21
22
22
Drycc charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
23
23
@@ -32,7 +32,7 @@ Drycc charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment a
32
32
To install the chart with the release name `my-release`:
|`volumePermissions.enabled`| Enable init container that changes the owner and group of the persistent volume(s) mountpoint to `runAsUser:fsGroup`|`false`|
|`volumePermissions.image.tag`| Init container volume-permissions image tag (immutable tags are recommended) |`11-debian-11-r39`|
308
308
|`volumePermissions.image.digest`| Init container volume-permissions image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag |`""`|
The above parameters map to the env variables defined in [bitnami/mysql](https://github.com/bitnami/containers/tree/main/bitnami/mysql). For more information please refer to the [bitnami/mysql](https://github.com/bitnami/containers/tree/main/bitnami/mysql) image documentation.
361
+
The above parameters map to the env variables defined in [drycc/mysql](https://github.com/drycc/containers/tree/main/drycc/mysql). For more information please refer to the [drycc/mysql](https://github.com/drycc/containers/tree/main/drycc/mysql) image documentation.
362
362
363
363
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
385
+
### [Rolling VS Immutable tags](https://docs.drycc.com/containers/how-to/understand-rolling-tags-containers/)
386
386
387
387
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
388
388
389
389
Drycc will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
390
390
391
391
### Use a different MySQL version
392
392
393
-
To modify the application version used in this chart, specify a different version of the image using the `image.tag` parameter and/or a different repository using the `image.repository` parameter. Refer to the [chart documentation for more information on these parameters and how to use them with images from a private registry](https://docs.bitnami.com/kubernetes/infrastructure/mysql/configuration/change-image-version/).
393
+
To modify the application version used in this chart, specify a different version of the image using the `image.tag` parameter and/or a different repository using the `image.repository` parameter. Refer to the [chart documentation for more information on these parameters and how to use them with images from a private registry](https://docs.drycc.com/kubernetes/infrastructure/mysql/configuration/change-image-version/).
394
394
395
395
### Customize a new MySQL instance
396
396
397
-
The [Drycc MySQL](https://github.com/bitnami/containers/tree/main/bitnami/mysql) image allows you to use your custom scripts to initialize a fresh instance. Custom scripts may be specified using the `initdbScripts` parameter. Alternatively, an external ConfigMap may be created with all the initialization scripts and the ConfigMap passed to the chart via the `initdbScriptsConfigMap` parameter. Note that this will override the `initdbScripts` parameter.
397
+
The [Drycc MySQL](https://github.com/drycc/containers/tree/main/drycc/mysql) image allows you to use your custom scripts to initialize a fresh instance. Custom scripts may be specified using the `initdbScripts` parameter. Alternatively, an external ConfigMap may be created with all the initialization scripts and the ConfigMap passed to the chart via the `initdbScriptsConfigMap` parameter. Note that this will override the `initdbScripts` parameter.
398
398
399
399
The allowed extensions are `.sh`, `.sql` and `.sql.gz`.
400
400
401
401
These scripts are treated differently depending on their extension. While `.sh` scripts are executed on all the nodes, `.sql` and `.sql.gz` scripts are only executed on the primary nodes. This is because `.sh` scripts support conditional tests to identify the type of node they are running on, while such tests are not supported in `.sql` or `sql.gz` files.
402
402
403
-
Refer to the [chart documentation for more information and a usage example](http://docs.bitnami.com/kubernetes/infrastructure/mysql/configuration/customize-new-instance/).
403
+
Refer to the [chart documentation for more information and a usage example](http://docs.drycc.com/kubernetes/infrastructure/mysql/configuration/customize-new-instance/).
404
404
405
405
### Sidecars and Init Containers
406
406
@@ -430,11 +430,11 @@ initContainers:
430
430
431
431
## Persistence
432
432
433
-
The [Drycc MySQL](https://github.com/bitnami/containers/tree/main/bitnami/mysql) image stores the MySQL data and configurations at the `/bitnami/mysql` path of the container.
433
+
The [Drycc MySQL](https://github.com/drycc/containers/tree/main/drycc/mysql) image stores the MySQL data and configurations at the `/drycc/mysql` path of the container.
434
434
435
435
The chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) volume at this location. The volume is created using dynamic volume provisioning by default. An existing PersistentVolumeClaim can also be defined for this purpose.
436
436
437
-
If you encounter errors when working with persistent volumes, refer to our [troubleshooting guide for persistent volumes](https://docs.bitnami.com/kubernetes/faq/troubleshooting/troubleshooting-persistence-volumes/).
437
+
If you encounter errors when working with persistent volumes, refer to our [troubleshooting guide for persistent volumes](https://docs.drycc.com/kubernetes/faq/troubleshooting/troubleshooting-persistence-volumes/).
438
438
439
439
## Network Policy
440
440
@@ -455,11 +455,11 @@ This label will be displayed in the output of a successful install.
455
455
456
456
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
457
457
458
-
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
458
+
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [drycc/common](https://github.com/drycc/charts/tree/master/drycc/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
459
459
460
460
## Troubleshooting
461
461
462
-
Find more information about how to deal with common errors related to Drycc's Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues).
462
+
Find more information about how to deal with common errors related to Drycc's Helm charts in [this troubleshooting guide](https://docs.drycc.com/general/how-to/troubleshoot-helm-chart-issues).
463
463
464
464
## Upgrading
465
465
@@ -481,7 +481,7 @@ Affected values:
481
481
- The way how passwords are handled has been refactored and value `auth.forcePassword` has been removed. Now, the password configuration will have the following priority:
482
482
1. Search for an already existing 'Secret' resource and reuse previous password.
483
483
2. Password provided via the values.yaml
484
-
3. If no secret existed, and no password was provided, the bitnami/mysql chart will set a randomly generated password.
484
+
3. If no secret existed, and no password was provided, the drycc/mysql chart will set a randomly generated password.
485
485
- `primary.service.port`was renamed as `primary.service.ports.mysql`.
486
486
- `secondary.service.port`was renamed as `secondary.service.ports.mysql`.
487
487
- `primary.service.nodePort`was renamed as `primary.service.nodePorts.mysql`.
@@ -500,7 +500,7 @@ Affected values:
500
500
- Credentials parameters are reorganized under the `auth` parameter.
501
501
- `replication.enabled` parameter is deprecated in favor of `architecture` parameter that accepts two values: `standalone`and `replication`.
502
502
- Chart labels were adapted to follow the [Helm charts standard labels](https://helm.sh/docs/chart_best_practices/labels/#standard-labels).
503
-
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
503
+
- This version also introduces `drycc/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/drycc/charts/tree/master/drycc/common#drycc-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
[On November 13, 2020, Helm v2 support formally ended](https://github.com/helm/charts#status-of-the-project). This major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
520
520
521
-
[Learn more about this change and related upgrade considerations](https://docs.bitnami.com/kubernetes/infrastructure/mysql/administration/upgrade-helm3/).
521
+
[Learn more about this change and related upgrade considerations](https://docs.drycc.com/kubernetes/infrastructure/mysql/administration/upgrade-helm3/).
0 commit comments