Kafka: 3. Pick the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. View the full guide here: Spin up a real Kafka service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically.

👋 Welcome to the Stackhero documentation!

Stackhero gives you a fully managed Kafka cloud environment, ready in minutes. Here is what you can expect:

  • No limits on message size or transfer: scale your data without worrying about caps.
  • Simple, one-click updates keep your platform current without downtime or manual work.
  • Consistent high performance and robust security on your own private, dedicated infrastructure.

If you want to move faster and reduce operational overhead, Stackhero provides Kafka cloud hosting to help you. You can have a production-ready cluster in about 5 minutes.

The examples below use the entry-level instance 10G for Kafka by default. This is a solid choice for most workloads, but you are welcome to adjust it as needed. To view all available instance types for Kafka, you can run:

# The NAME column shows the value to pass to --instance
stackhero instances-store-list --service-store=kafka

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Spin up a real Kafka service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically
  2. 1. Create an access token and store it as a CI secret
  3. 2. The lifecycle script
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for Kafka

  1. Automate with the CLI
    Start Kafka, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI