* Do not use 'master' in release name when replication is not enabled
* Do not use 'master' in release name when replication is not enabled
* Use the same version in the Chart.yaml and in the values.yaml. Most of the web apps are compatible with 10.1 right now
* Updated Joomla! to use latest MariaDB chart
* Updated Joomla! to use latest MariaDB chart
* Update minor version
* Update MariaDB chart version
* Updated Joomla! to use latest MariaDB chart
* Updated Joomla! to use latest MariaDB chart
* Update MariaDB chart version
* Increase the Joomla! Chart versio
* Update readme options and bump the Joomla version
* adding https option to use ACM in AWS and also whitelisting for service type LoadBalancer
* fixing check for range of IPs
* removing extraneous space
* adding description of value
* bumping version
* bumping to 1.6.0
* Expose liveness/readiness probes to values.yaml
* Add newline at the end of values.yaml
* bump chart version
* Edit default value for initialDelaySeconds
* Undo mariadb update
Adds the ability to specify the kubernetes.io/ingress.class value to
watch for.
The Traefik chart currently allows filtering by ingress label selector,
but ingress annotations are more commonly supported in charts than
ingress labels (see e.g. the stable/dashboard and stable/prometheus
charts). Supporting ingress class specification allows users to easily
have multiple Traefik instances (e.g. internal vs external) filtering on
this standard annotation.
The previous information around supported k8s versions in the rabbitmq
chart was incorrect. It said this chart could be used with k8s 1.4+ with
the beta APIs enabled. However, the statefulset utilized
apps/v1beta2, which is only available in 1.8+. Supporting 1.8+
corresponds with the overall Charts policy of supporting the current and
previous minor release (in this case, 1.10 and 1.9).)
The previous information around supported k8s versions in the `redis`
chart was incorrect. It said this chart could be used with k8s 1.4+ with
the beta APIs enabled. However, the `statefulset` utilized
`apps/v1beta2`, which is only available in 1.8+. Supporting 1.8+
corresponds with the overall Charts policy of supporting the current and
previous minor release (in this case, 1.10 and 1.9).
* Do not use 'master' in release name when replication is not enabled
* Do not use 'master' in release name when replication is not enabled
* Use the same version in the Chart.yaml and in the values.yaml. Most of the web apps are compatible with 10.1 right now
* Update minor version
* Update component versions
* Bump Spinnaker version in Chart.yaml
* Use either local or kubeconfig accounts
* Update docs for spinnaker multicluster
* Fix capitalization of values
* Fix README indentation
* Add more info to values file
* Bump Spinnaker chart minor version
* Only mount secrets if kubeConfig is enabled
* first draft
* allow to connect for web if host not passed
* moved to stable folder
* removed from incubator
* added readme and notes
* rename properly
* fix lint errors
* fixes for juans review
* fix typo
* unguiculus feedback
* improvements to how the db fullname template was named
* sameersbn feedback
* readibility improvements
* fixes to sameer's review
* rename suffix to chartName
* rename part2
* Update jaeger version to 1.4.1, but use a single value for all 4 images as they all need to use a single consistent version
* Update chart version
* Update chart version to 0.5.0
The containers in the stateful set were ignoring the resource requests
when specified in `values.yaml`. Comment out the resources requests
in `values.yaml`, so we only set requests if the user specifically
enables them.
I verified this is working by running `kubectl describe pod POD | grep
cpu` on one of the created pods on the fix branch. It returned `cpu:
"100m"`. On the master branch, the same command returned nothing.