| const zlib = require('zlib'); | |
| const concatStream = require('concat-stream'); | |
| const BufferHelper = require('bufferhelper'); | |
| const { debugLogger } = require('../../utils/logger'); | |
| /** | |
| * Modify the response | |
| * @param res {Object} The http response | |
| * @param contentEncoding {String} The http header content-encoding: gzip/deflate | |
| * @param callback {Function} Custom modified logic |
| # Check list of available schemas | |
| curl http://localhost:8081/subjects | |
| # Expected output: | |
| # ["app-users-value", "app-movies-value"] | |
| # Check detail of app-users-value schema | |
| curl http://localhost:8081/subjects/app-users-value/versions/latest | |
| # Expected output: |
| # Enter Kafka Shell Client | |
| make kafka-shell | |
| # Assign topic name in variable | |
| TOPIC=test | |
| # Consumer for console text output, no stream offset | |
| kafka-console-consumer --topic=$TOPIC --bootstrap-server=$BROKERS --from-beginning | |
| # Console consumer will print each records in the topic |
| # Assign 1 public subnetID from above subnet setup | |
| SUBNET_ID=${subnetID} | |
| # List all kafka cluster for corrsponding region | |
| aws kafka list-clusters --region us-east-1 | |
| # Expected output | |
| # { | |
| # "ClusterInfoList": [ | |
| # { |
| # 0. Delete the existing topics: app-users, app-movies | |
| make kafka-shell | |
| kafka-topics --delete --topic app-users --zookeeper $ZK | |
| kafka-topics --delete --topic app-movies --zookeeper $ZK | |
| kafka-topics --create --topic app-users --partitions 2 --zookeeper $ZK --replication-factor 2 | |
| kafka-topics --create --topic app-movies --partitions 2 --zookeeper $ZK --replication-factor 2 | |
| exit |
| # Enter Kafka Connect Shell Client | |
| make connect-shell | |
| # Kafka Connect with connect-standalone setting, connecting via postgres | |
| connect-standalone dev/connect-standalone.properties dev/source-postgres-incremental.properties | |
| # Expected console-consumer output from topic: app-users | |
| # { | |
| # "schema":{"type":"struct","fields":[{"type":"int32","optional":false,"field":"id"},{"type":"string","optional":false,"field":"first_name"},{"type":"string","optional":false,"field":"last_name"},{"type":"string","optional":false,"field":"email"}],"optional":false,"name":"users"}, | |
| # "payload":{"id":101,"first_name":"Cass","last_name":"Truss","email":"ctruss0@salon.com"} |
| # Enter Kafka Shell Client | |
| make kafka-shell | |
| # Assign topic name in variable | |
| TOPIC=test | |
| # Producer for console text input | |
| kafka-console-producer --topic=$TOPIC --broker-list=$BROKERS | |
| ############################################### |
| # Enter Kafka Shell Client | |
| make kafka-shell | |
| # Assign testing topic name in variable | |
| TOPIC=test | |
| # Describe all topic | |
| kafka-topics --describe --zookeeper $ZK | |
| # Create topic |
Yes - you can create a Kubernetes cluster with Raspberry Pis with the default operating system called Raspbian. This means you can carry on using all the tools and packages you're used to with the officially-supported OS.
This is part of a blog post Serverless Kubernetes home-lab with your Raspberry Pis written by Alex Ellis.
Copyright disclaimer: Please provide a link to the post and give attribution to the author if you plan to use this content in your own materials.
| export default { | |
| LIST_ITEM: 'listItem', | |
| }; |