* MySQL service endpoints shouldn't depend on /metrics
Problem: mysqld_metrics doesn't respond on "/metrics" when dropping big database. As result service has no endpoint because metrics cann't be queried.
Solution: use "/" for httpGet probes on metrics which will return only landing page with http code 200.
* Update Chart.yaml
* [stable/mysql] Support extra{Volumes,VolumeMounts,InitContainers}
* [stable/mysql] Use tpl on extra{Volumes,VolumeMounts}
Bump the version from 0.9.0 to 0.9.1 to avoid conflicts on my end.
* Make liveness and readiness settings configurable for the metrics container
* Bump mysql chart version to 0.8.3, add metrics container's probe config to README.md
* change port-forward to single command
forward service instead of pod - bit more readable
* remove port 3306 defaults
* version bump
* remove double up values.service.port
* [stable/mysql] Add ability to modify timezone (#7121)
* Add a 'timezone' to allow timezone to be configured via TZ env
* Bump version number
* Slightly more descriptive README.md
* Add nodeSelector config parameter to mysql chart
* Add appVersion
* Rerun ci
* Add prometheus metrics
* Add new chart version
* Add metrics to service
* Fix hardcode annotations
* Fix maintainer name
Also, update the conditional logic in the mysql.fullname template to more
closely mirror the behaviour of other charts, i.e. if no fullnameOverride is
specified and the release name contains the chart name, use it as the full name.
* [stable/mysql] add option to run sql script post container start
- add ConfigMap for sql initialization files
- mount initialization files to /docker-entrypoint-initdb.d if present
* update README to reflect initdb filetypes and startup behaviour
* increase chart version
* increase minor version, fix typo
* split configmap into seperate files
* Adding BYO ssl certificate option for secure connections to MySQL
* Updating README w/SSL options.
* Removing CA option from SSL test. This will fail if the certificate is self-signed.
* Bumping minor version to signify new features and after rebase
* Fixing helm test for default values.
* Allowing user to manage SSL secrets externally
* Updating SSL documentation
The MySQL chart only allowed the service type to be ClusterIP,
preventing its use with Minikube. This patch adds the ability to create
the service with the `NodePort` type.
Drive-by:
* Update the `NOTES.txt` file to provide similar instructions to the
PostreSQL chart.
* typo fix and add --purge to helm delete
typo fix and add --purge to helm delete
* removing the --purge as requested by maintainer.
* Update Chart.yaml
* Set default imagePullPolicy to IfNotPresent
Fixes#295 for MySQL chart in the same way as #309 does it for MariaDB.
Related to kubernetes/kubernetes#38542.
PS I've changed `pod.alpha.kubernetes.io/init-containers` to
`pod.beta.kubernetes.io/init-containers`.
* Update docs about updating images
When `persistance.enabled` is set to `false`, `emptyDir` volume is
mounted as `/var/lib/mysql` and `rmdir /var/lib/mysql/lost+found` fails
because the directory is not there.
```
2m 5s 12 {kubelet minikube} Warning FailedSync Error syncing pod, skipping: [failed to "InitContainer" for "remove-lost-found" with RunInitContainerError: "init container \"remove-lost-found\" exited with 1", failed to "StartContainer" for "remove-lost-found" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=remove-lost-found pod=pruning-bunny-mysql-3645202232-9md2n_default(c5e4252e-9699-11e6-97b4-da01ddf400ca)"
```
The pod template labels are used as selectors for the deployment, so
they should be the minimal required to uniquely select the
ReplicaSets/Pods. See https://github.com/kubernetes/helm/issues/1390 for
more info about this change.