aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Sets other useful labels, for #78 and #56Staffan Olsson2018-01-082-7/+9
|
* Revert "Deprecates our own statefulset pod label kafka-broker-id"Staffan Olsson2018-01-082-3/+0
| | | | This reverts commit 096e3bdfba31d2918520011886a6a0d1f1b08c84.
* Adds the required RBAC for the init script to set the kafka-broker-id labelStaffan Olsson2018-01-081-0/+41
|
* Merge pull request #115 from StevenACoffman/cleanupsolsson2018-01-084-7/+5
|\ | | | | Minor cleanups
| * cleanup: Minor cleanupsSteve Coffman2018-01-054-7/+5
|/
* Merge pull request #92 from Yolean/1.8-kube-eventssolsson2017-12-183-0/+170
|\ | | | | Stream kube events to topic, as opt-in folder instead of addon
| * Modernize based on1.8-kube-eventsStaffan Olsson2017-12-183-38/+6
| | | | | | | | | | | | | | * https://github.com/Yolean/kubernetes-kafka/pull/107 * https://github.com/Yolean/kubernetes-kafka/issues/101 * https://github.com/Yolean/fluent-bit-kubernetes-kafka/commit/e045ef1ef03f9fd299575a7aa9ca312e6687e441 * https://github.com/Yolean/kubernetes-kafka/pull/52
| * Uses kafkacat build as in tests and logs-streamingStaffan Olsson2017-11-091-1/+1
| |
| * Fixes manifest. I must have had a local edit last time.Staffan Olsson2017-10-301-1/+1
| |
| * Merge pull request #86 from Yolean/atamon-patch-1solsson2017-10-301-2/+2
| |\ | | | | | | Fix retention from 0.8 days to 8 days
| | * Fix retention from 0.8 days to 8 daysatamon-patch-1Anton Lindgren2017-10-301-2/+2
| |/ | | | | | | | | Silly change, but 0.8 days is very short. Google helped me verify the math.
| * Aligns RBAC with addons->folders for v3.0.0Staffan Olsson2017-10-271-0/+0
| |
| * Fixes JSON syntax, topic is jq:able nowStaffan Olsson2017-10-271-2/+2
| |
| * Needs to be tweaked depending on the churnStaffan Olsson2017-10-271-1/+1
| |
| * An actual assertionStaffan Olsson2017-10-271-10/+72
| |
| * Manifests updated to 1.8 and v3.0.0 pre-mergeStaffan Olsson2017-10-273-2/+10
| |
| * kafkacat's debug output solves the silence, but ...Staffan Olsson2017-10-261-2/+0
| | | | | | | | | | | | to see the error message (like missing RBAC) you basically have to run the curl command. I'd like startup to be as fast as possible, to not miss events, so I hesitate to add checks.
| * bash -e is important, in combination with curl -f, so ...Staffan Olsson2017-10-261-12/+2
| | | | | | | | | | we don't send error messages to the topic (even if it's json -- format is different and it's pretty printed)
| * Argh, curl will pretty print the json ...Staffan Olsson2017-10-261-1/+11
| | | | | | | | and kafkacat will produce each line separately
| * Makes things a bit less obscure if for example RBAC failsStaffan Olsson2017-10-261-2/+12
| |
| * Use an image with new kafkacat and curl versionsStaffan Olsson2017-10-261-1/+1
| |
| * Not a proper test yet, but the PR documents how to use it to see eventsStaffan Olsson2017-08-051-7/+2
| |
| * Moves the example comsumer to the test namespaceStaffan Olsson2017-08-051-5/+4
| |
| * Adds RBAC policy for curl, default service accountStaffan Olsson2017-08-051-0/+30
| |
| * Latest build suppors snappy compressionStaffan Olsson2017-08-052-2/+2
| |
| * Works with my current kafka image, and the test consumer still sees JSONStaffan Olsson2017-08-051-1/+1
| |
| * Testing compression but solsson/kafka:0.11.0.0 throws ...Staffan Olsson2017-08-051-0/+1
| | | | | | | | | | | | | | | | | | Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy at org.xerial.snappy.SnappyInputStream.readFully(SnappyInputStream.java:145) at org.xerial.snappy.SnappyInputStream.readHeader(SnappyInputStream.java:99) at org.xerial.snappy.SnappyInputStream.<init>(SnappyInputStream.java:59) at org.apache.kafka.common.record.CompressionType$3.wrapForInput(CompressionType.java:82) ... 40 more
| * Produces proper json. Let's see when curl gives up and the container restarts.Staffan Olsson2017-08-051-2/+1
| |
| * Quite interesting way to test a command from yaml - see it in logsStaffan Olsson2017-08-051-1/+3
| |
| * wipStaffan Olsson2017-08-051-5/+6
| |
| * Produces and reads eventsStaffan Olsson2017-08-053-2/+72
| |
| * Creates a pod for expermentation with kubectl and kafkacatStaffan Olsson2017-08-051-0/+27
| |
* | Merge pull request #107 from Yolean/yolean-topic-managementsolsson2017-12-183-56/+25
|\ \ | | | | | | Embrace auto.topic.create; trust defaults for production topics
| * | Deprecates our own statefulset pod label kafka-broker-idyolean-topic-managementStaffan Olsson2017-12-142-0/+3
| | |
| * | I find it scary when broker start logs:Staffan Olsson2017-12-141-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
| * | Merge branch 'topic-config-together' into yolean-topic-managementStaffan Olsson2017-12-132-60/+21
| |\ \
| | * | Now was a good time to get rid of the last --overrideStaffan Olsson2017-12-132-3/+1
| | | | | | | | | | | | | | | | as we now encourage close scrutiny of the config file.
| | * | Moves the essential data path config to theStaffan Olsson2017-12-132-3/+1
| | | | | | | | | | | | | | | | config location suggested by Kafka's sample conf.
| | * | Permanent retention is a friendlier default,Staffan Olsson2017-12-132-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 topStaffan Olsson2017-12-131-52/+19
| |/ /
| * | Gathers the config that has to do with topic creationStaffan Olsson2017-12-132-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 addingStaffan Olsson2017-12-131-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 factorStaffan Olsson2017-12-011-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 #104 from StevenACoffman/ADD_AWSsolsson2017-12-082-0/+20
|\ \ \ | |/ / |/| | ADD_AWS: Add AWS storage classes
| * | ADD_AWS: Add AWS storage classSteve Coffman2017-12-082-0/+20
|/ /
* | Removes some "platform" ideas from readme as they need real PRsStaffan Olsson2017-12-011-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rather than a couple of sentences. In response to #103. Regarding Kafka Streams I no longer think we need examples, because any dockerized streams application can run as a deployment. An example of Kafka Connect would be useful, in particular the combination of a custom image (or one with stock connectors) and a Connect cluster manifest. This is tracked in #69, but not the relation to https://github.com/solsson/dockerfiles/tree/master/connect-* KSQL (#68) is highly interesting.
* | Merge pull request #96 from Yolean/enable-broker-jmxsolsson2017-11-101-0/+4
|\ \ | | | | | | Enable broker JMX_PORT 5555
| * | Exposes JMX for brokers, to typical monitoring setupsenable-broker-jmxStaffan Olsson2017-11-091-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.
* | | Merge pull request #94 from Yolean/restore-ondelete-behaviorv3.0.1solsson2017-11-093-0/+6
|\ \ \ | |/ / |/| | Disables RollingUpdate, i.e. reverts to pre-1.7 behavior
| * | Sets OnDelete explicitly, as RollingUpdate is a new defaultrestore-ondelete-behaviorStaffan Olsson2017-11-093-0/+6
|/ / | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-25 12:53:48 +0000