* Add scaffolding for CouchDB chart
* Move to a StatefulSet rather than a Deployment
* Configure a headless service
This configuration is necessary to ensure that the individual Pods
have well-defined hostnames that are discoverable via DNS.
* Make the minimal set of changes for a StatefulSet
Lots of these changes need to be properly parameterized, but first
let's get the basics working.
* Fix the default variables for a 3 node cluster
* Support generic Erlang VM flags as Values
* Specify the location of sidecar image in values
* Allow to override the podManagementPolicy
* Ensure exact match between labels and selector
* Simplify headless service definition
The current version of the sidecar container expects the headless
service to export SRV records for a _couchdb service, so there's no
point in parameterizing the name here. In theory the port could be
omitted, but there are a few unresolved issues with that configuration
as of v1.7 so we just put in the stock CouchDB port number.
* Do not pretend that we configure the CouchDB port
In a future version we may be able to pass the port configuration to
CouchDB using a ConfigMap, but for now the port on which the Pods are
listening for HTTP requests is fixed.
* Enable configuration of PVCs for the statefulset
* Choose a more user-friendly name for spec.replicas
Users familiar with CouchDB may wonder if "replicaCount" refers to the
desired number of replicas per document, as opposed to the size of the
cluster.
* Clean up comments, improve example resource limit
* Improve the Service / Ingress configuration
This re-adds a traditional Service alongside the headless one so
clients have a stable way to access the CouchDB cluster. It also
refines some of the documentation around the Ingress resource.
* Update the chart metadata
* Add a basic README
* Make some small doc changes to align w/ standards
* Enable CouchDB configuration through ConfigMap
* Configure admin account, cookie auth using Secrets
* Tell the user to run finish_cluster after startup
* Tweak the notes to use interactive password prompt
* Fix the database-storage mount point
* Automatically create admin account secrets
This change enables the chart to be automically installed in a secure
fashion with a single command.
* Use GitHub username for maintainer name
* Target latest StatefulSet API
This also means we require Kube 1.8.
* Removed Postgresql own deployment and created dependency to stable/Postgresql.
Updated artifactory version number to 5.8.0.
Updated notes and added ingress documentation.
Added Ingress support to artifactory.
Made the NGINX deployment optional by adding an enabled flag.
Fixed naming of components.
* bump chart version
* Fixed wrong Chart number for artifactory
* Add documentation for Ingress, set Postgresql chart version, set persistence default on true
* Refresh requirements.lock
* Set version to 7.0.0, cecause the API to the chart changed
* revert deletion of RABBITMQ_VHOST environment variable to restore the ability to configure vhosts for bitnami/rabbitmq images
* bump rabbitmq chart version
* removes unused RABBITMQ_DEFAULT_VHOST env variable
* bump version to 0.6.17
* Update nginx/ingress controller to 0.9.0 release
* Update config defaults in nginx-ingress README
* Bump nginx-ingress chart version to 0.8.23
* Use semverCompare for nginx-ingress annotation prefix
* Add nginx-ingress annotation prefix to daemonset
* Update upstream version to 0.10.2
* Bump chart version to 0.9.0
* Remove annotations-prefix flag
* Apply 0.9.x flags to any version 0.9.0-beta.1 and above
Stolen from PR #3369
* Update default image tag in README
* Allows override for KAFKA_ADVERTISED_LISTENERS
* Appends to advertised listeners, rather than replacing
* Adds configurationOverride (same as default) to satisfy helm lint
* [stable/kong] Add a chart for Kong
- Chart deploys Kong and its backing datastore either Cassandra or
PostgreSql(default)
- Uses official [Kong](https://hub.docker.com/_/kong/) Docker image
* Deployment apiversion update
* added missing selector field
* added release to selector
* update to support Kong v0.12.1
* fix indentation
* [stable/kubernetes-dashboard] Make chart more standardized
The charts ecosystem seems to be converging on some standards, which
seems to be driven by the patterns laid out in `helm create`. This makes
the following breaking changes to this crate:
* move the image definition into a map
* move the service definition into a map
* rename httpPort to externalPort
* reordered files to match the `helm create` order
* Made sure chart names don't contain '+'
Finally this bumps the version from 0.4 to 0.5 since this is not
backwards compatible.
* [stable/kubernetes-dashboard] allow for custom deployment and service labels
* [stable/kubernetes-dashboard] allow service name to be overridden
Closes#2099.
* [stable/kubernetes-dashboard] Add links and the k8s logo
* Update Datadog chart to prepare for agent6
- upgrade kube-state-metrics dependency
- use DD_ prefixed envvars when supported by agent5
- add commented lines for using agent6 images
- cleanup pod specs: remove empty envvars and volumes
- remove kubernetes_state.yaml autoconf as it's shipped by default
- update readme
* fix ressources in spec, fixes#2930
* linting
Use case: I want to avoid running Consul on certain nodes, such
as preemptible nodes in a Google Kubernetes Engine node pool.
The current antiAffinity setting makes this pull request a bit hacky,
but this was the quickest way to simply get my functionality running.
I definitely wouldn't like to have it merged as it is right now ;)
Are you open to having the current affinity settings as a whole
be a bit more customizable? I imagine there might be other users
with this use case.
* [incubator/patroni] updates etcd dependency to latest version 0.3.6
This is just to keep dependencies recent and to escape deprecations
from the etcd chart.
* [incubator/patroni] bump version to 0.5.1
* [stable/anchore-engine] Updates and bug fix
Fixes bug in configuration of policy bundle sync.
Updates NOTES.txt and README.md for a bit more detail.
* Bump anchore-engine chart version to 0.1.1
* Update stable/anchore-engine readme to include config option for ingress and loadbalancer