kubernetes-kafka - Kafka cluster as Kubernetes StatefulSet, plain manifests and config

	Commit message (Collapse)	Author	Age	Files	Lines
*	Uses brokers' default replication factor for explicit topic creationuse-default-replication-factor	Staffan Olsson	2018-01-22	2	-4/+0
\|
*	Sets all labels at the end of the init script,broker-init-pod-labler	Staffan Olsson	2018-01-08	1	-5/+8
\| \| \| \| \| \|	to speed up a bit and reduce the risk that it interferes with actual config. Also if the init script goes crash looping you won't get warnings about labels already being set.
*	Sets other useful labels, for #78 and #56	Staffan Olsson	2018-01-08	1	-2/+5
\|
*	Revert "Deprecates our own statefulset pod label kafka-broker-id"	Staffan Olsson	2018-01-08	1	-1/+0
\| \| \| \|	This reverts commit 096e3bdfba31d2918520011886a6a0d1f1b08c84.
*	cleanup: Minor cleanups	Steve Coffman	2018-01-05	3	-6/+5
\|
*	Deprecates our own statefulset pod label kafka-broker-idyolean-topic-management	Staffan Olsson	2017-12-14	1	-0/+1
\|
*	I find it scary when broker start logs:	Staffan Olsson	2017-12-14	1	-0/+1
\| \| \| \| \| \| \|	log.dir = /tmp/kafka-logs log.dirs = /var/lib/kafka/data/topics but this is the lesser of two evils compared to duplicate values
*	Now was a good time to get rid of the last --override	Staffan Olsson	2017-12-13	2	-3/+1
\| \| \| \|	as we now encourage close scrutiny of the config file.
*	Moves the essential data path config to the	Staffan Olsson	2017-12-13	2	-3/+1
\| \| \| \|	config location suggested by Kafka's sample conf.
*	Permanent retention is a friendlier default,	Staffan Olsson	2017-12-13	2	-3/+1
\| \| \| \| \| \| \|	and easy to reconfigure per topic as they grow. We already had that, but this branch cares about grouping such conf. It also encourages topic defaults geared towards persistent data.
*	Places the values that are most likely to need attention at the top	Staffan Olsson	2017-12-13	1	-52/+19
\|
*	Gathers the config that has to do with topic creation	Staffan Olsson	2017-12-13	2	-2/+3
\| \| \| \| \| \| \|	in one place. These values are critical to maintain for those, like us, who make use of auto create topics for production data. Also a step towards #72 and #77.
*	Enables auto create topics because there's use cases for adding	Staffan Olsson	2017-12-13	1	-1/+1
\| \| \| \| \| \| \|	topics at runtime, such as splitting a stream based on some business enum. Producers and Kafka Streams apps would otherwise need to set up an AdminClient to do that. This reverts commit: 0681cc515fa1c505b905ef60c7d3132e8d7510af
*	Lets clusters define their preferred (prod) replication factor	Staffan Olsson	2017-12-01	1	-0/+3
\| \| \| \| \|	so that we can omit replication-factor when creating topics, as we benefit from reusing such commands or definitions across dev-qa-prod.
*	Merge pull request #96 from Yolean/enable-broker-jmx	solsson	2017-11-10	1	-0/+4
\|\ \| \| \| \|	Enable broker JMX_PORT 5555
\| *	Exposes JMX for brokers, to typical monitoring setupsenable-broker-jmx	Staffan Olsson	2017-11-09	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Already included in #49, but here we don't add any export container to the pod. Can be utilized by kafka-manager (#83) - just tick the JMX box when adding a cluster - to see bytes in/out rates.
* \|	Sets OnDelete explicitly, as RollingUpdate is a new defaultrestore-ondelete-behavior	Staffan Olsson	2017-11-09	1	-0/+2
\|/ \| \| \| \| \| \| \|	Due to the use of config map for most of the conifg, RollingUpdate will be surprising, while still not preventing running pods that don't have the applied configuration. An automation effort would be required for proper RollingUpdate behavior.
*	Fixes a test issue at start and at consumer error1.8-manifests	Staffan Olsson	2017-11-09	1	-0/+2
\|
*	Makes kafka a feature folder too, consistent with the rest	Staffan Olsson	2017-11-09	8	-0/+741