* Reworked the logic around joining peers to make it a bit more aggressive and accurate when dealing with high-latency DNS resoltuion.
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* [stable/consul] Reworked wan peer to use the same logic as lan peer
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* [stable/consul] Skip joining WAN if wan_peers is not set
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* Updated chart version/values/readme
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* Added better logging around waiting for peers
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* Bump consul version as well
Signed-off-by: Oliver Isaac <oisaac@gmail.com>
* Add the ability to attach lifecycle options to StatefulSet
Add sample to values file
Bump chart version
Signed-off-by: Scott Hawkins <scott@articulate.com>
Signed-off-by: echoboomer <scott@articulate.com>
* Fix space in values file
Signed-off-by: echoboomer <scott@articulate.com>
* [stable/consul] update to latest
Signed-off-by: Carlos Alexandro Becker <caarlos0@gmail.com>
* fix: readme
Signed-off-by: Carlos Alexandro Becker <caarlos0@gmail.com>
* Added an option for consul-ui to specify extra annotations
Signed-off-by: natebwangsut <nate.bwangsut@gmail.com>
* Bump chart version
Signed-off-by: natebwangsut <nate.bwangsut@gmail.com>
* consul-improvements - ability to reuse gossip-key
* Reuse gossip key if already present as a k8s secret
* consul-improvements - increment chart version
* consul-improvements - don't force name change
* update version to 2.0.0
* added extra configuration options for consul
* fixed readme
* added pitfall for ACLs
* added a note about configuration updates
* updated documentation syntax and added example
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.
* Update consul image to 1.0.0
This fixes a lot of the stability issues on k8s
* Add pod anti affinity to spec
This ensures a single node failure doesn't take out multiple consul services
* Use the rolling update strategy for updates
* Add a pod disruption budget
* Bump chart version
* Update README to reflect ImageTag update
* Make anti-affinity settings configurable in Values.yaml
* Bump [stable/consul] to 1.0.0
* Bump consul version to 0.8.3
Add app version tag
Update chart maintainers to github username
Add consul helm tests
Update documentation
Remove existing test.sh
* Update helm test command in notes
* (feat/upgrade-statefulset): Update consul chart to Statefulset
Update to StatefulSet
Update storage annotations
Remove ReadinessProbe as it causes race condition
Update documentation
* Rename manifest
* fix image tag to match new upstream convention
* update README variables
Add helper template
Add NOTES
Add storageclass variable
Conditional creation of UI service
* Add livelinessprobe
* Moved to stable
* update gotemplates to support longer names
* added backwards compatible storage notation
* Update to 0.7.5
* Fix broken values from rebase.
* Ensure ui values are uniform
* Make secret name unique
* 0.7.4 is the latest published.
* Increase timeout to give bootstrapping long enough
This is not an ideal solution, but it's not easy to get a self
health status. This is the best we can do.
* Really bump to 0.7.5 now it's released.
* Fix typo.
* Fix name
* Update chart description
* fix typos in config params
* use fullname partial for secret name
* updated secret name volume