From 6996463372108d392af205294710133bf027b2d9 Mon Sep 17 00:00:00 2001 From: Roko Kruze Date: Mon, 11 Jan 2021 14:57:52 -0800 Subject: [PATCH] Quickstarts for a number of different ways to install Redpanda Quickstarts for docker, K8, mac and linux. Broke out the production deployment to a separate page. Added a FAQ. --- docs/www/faq.md | 25 +++ docs/www/production-deployment.md | 289 +++++++++++++++++++++++++++++ docs/www/quick-start-docker.md | 158 ++++++++++++++++ docs/www/quick-start-kubernetes.md | 94 ++++++++++ docs/www/quick-start-linux.md | 66 +++++++ docs/www/quick-start-macos.md | 45 +++++ docs/www/rpk-container-guide.md | 64 +++++++ 7 files changed, 741 insertions(+) create mode 100644 docs/www/faq.md create mode 100644 docs/www/production-deployment.md create mode 100644 docs/www/quick-start-docker.md create mode 100644 docs/www/quick-start-kubernetes.md create mode 100644 docs/www/quick-start-linux.md create mode 100644 docs/www/quick-start-macos.md create mode 100644 docs/www/rpk-container-guide.md diff --git a/docs/www/faq.md b/docs/www/faq.md new file mode 100644 index 000000000000..2852d050936a --- /dev/null +++ b/docs/www/faq.md @@ -0,0 +1,25 @@ +--- +title: Frequently Asked Questions +order: 0 +--- +# Frequently Asked Questions + +## Is Redpanda Fully Kafka API Compatible? + +We support all parts of the Kafka API except for the transactions API. We are +working on adding this shortly and you can find the issue in our public +github here, [Support the Kafka Transactions API](https://github.com/vectorizedio/redpanda/issues/445). + +If you run into any issues while working with a Kafka tool, please let us know! [File an issue](https://github.com/vectorizedio/redpanda/issues/new) + +## Does Redpanda use Zookeeper? + +No, Redpanda is a modern streaming platform that has been built using C++ and +Raft for consensus. Since we use Raft we have no need for an external consensus +system like Zookeeper. + +## Can I run Redpanda directly on Windows or MacOS? + +Unfortunately, you can only run Redpanda directly on Linux. However, you can +use Docker to run Redpanda on any system supported by Docker. Please see our +[Quick Start Docker Guide](quick-start-docker.md) for more information. diff --git a/docs/www/production-deployment.md b/docs/www/production-deployment.md new file mode 100644 index 000000000000..a7492cdd9afa --- /dev/null +++ b/docs/www/production-deployment.md @@ -0,0 +1,289 @@ +--- +title: Production Deployment +order: 0 +--- +# Production Deployment + +This guide will take you through what is needed to setup a production cluster +of Redpanda. + +### Requirements + +For the best performance the following are strongly recommended: + +- XFS for the data directory of Redpanda (/var/lib/redpanda/data) +- A kernel that is at least 3.10.0-514, but a 4.18 or newer kernel is preferred +- Local NVMe, RAID-0 when using multiple disks +- 2GB of memory per core +- The following ports need to be opened + - `33145` - Internal RPC Port + - `9092` - Kafka API Port + - `9644` - Prometheus & HTTP Admin port + +## Installation + +First we need to provision the hardware needed. This can be done [manually](#manual-installation) or with the provided Terraform deployment files found here: [https://github.com/vectorizedio/deployment-automation]. + +First, install Terraform using the [Terraform Installation Tutorial](https://learn.hashicorp.com/tutorials/terraform/install-cli). +Then clone the `deployment-automation` repo: + +``` +git clone git@github.com:vectorizedio/deployment-automation.git +``` + +Then change into the directory: + +``` +cd deployment-automation +``` + +From here you can follow the specific instructions for [AWS](#aws) or +[GCP](#gcp) + +### AWS + +Within the `deployment-automation` folder change into the `aws` directory + +``` +cd aws +``` + +#### Step 1: Set AWS Credentials + +First we need to set the AWS secret and key. Terraform provide multiple ways +to set this which is covered here: [https://registry.terraform.io/providers/hashicorp/aws/latest/docs#environment-variables] + +#### Step 2: Init Terraform + +Before using Terraform to deploy the cluster we need to run the following: + +``` +terraform init +``` + +#### Step 3: Create the Cluster + +We now can run `terraform apply` to create the cluster. There are a number of +configuration options which can be specified when creating the cluster: + +- `aws_region`: The AWS region to deploy the infrastructure on. Default: `us-west-2`. +- `nodes`: The number of nodes to base the cluster on. Default: `1`. +- `enable_monitoring`: Will create a prometheus/grafana instance to be used for monitoring the cluster. Default: `true`. +- `instance_type`: The instance type which redpanda will be deployed on. Default: `i3.8xlarge`. +- `prometheus_instance_type`: The instance type which prometheus and grafana will deployed on. Default: `c5.2xlarge`. +- `public_key_path`: Provide the path to the public key of the keypair used to access the nodes. Default: `~/.ssh/id_rsa.pub` +- `distro`: Linux distribution to install (this settings affects the below variables). Default: `ubuntu-focal` +- `distro_ami`: AWS AMI to use for each available distribution. +These have to be changed with according to the chosen AWS region. +- `distro_ssh_user`: User used to ssh into the created EC2 instances. + +The following is an example of creating a three node cluster using i3.large +instances. + +``` +terraform apply -var="instance_type=i3.large" -var="nodes 3" +``` + +### GCP + +Within the `deployment-automation` folder change into the `gcp` directory + +``` +cd gcp +``` + +#### Step 1: Prerequisites + +You will need an existing subnet to deploy the VMs into. The subnet's attached +firewall should allow inbound traffic on ports 22, 3000, 8888, 8889, 9090, +9092, 9644 and 33145. This module adds the `rp-node` tag to the deployed VMs, +which can be used as the target tag for the firewall rule. + +#### Step 2: Init Terraform + +Before using Terraform to deploy the cluster we need to run the following: + +``` +terraform init +``` + +#### Step 3: Create the Cluster + +We now can run `terraform apply` to create the cluster. There are a number of +configuration options which can be specified when creating the cluster: + +- `region` (default: `us-west-1`): The region to deploy the infrastructure on. +- `zone` (default: `a`): The region's zone to deploy the infrastructure on. +- `subnet`: The name of an existing subnet to deploy the infrastructure on. +- `nodes` (default: `1`): The number of nodes to base the cluster on. Keep in mind that one node is used as a monitoring node. +- `disks` (default: `1`): The number of **local** disks to deploy on each machine +- `image` (default: `ubuntu-os-cloud/ubuntu-1804-lts`): The OS image running on the VMs. +- `machine_type` (default: `n2-standard-2`): The machine type. +- `public_key_path`: Provide the path to the public key of the keypair used to access the nodes. +- `ssh_user`: The ssh user. Must match the one in the public ssh key's comments. + +The following is an example of creating a three node cluster using the subnet +named `redpanda-cluster-subnet` + +``` +terraform apply -var nodes=3 -var subnet=redpanda-cluster-subnet -var public_key_path=~/.ssh/id_rsa.pub -var ssh_user=$USER +``` + +## Install Redpanda + +Once the hardware has been provisioned. You can choose to either install +Redpanda using our provided Ansible Playbooks or install Redpanda manually. + +- [Installation with Ansible](#Installation-with-Ansible) +- [Manual Installation](#Manual-Installation) + +## Installation with Ansible + +### Requirements + +- Install Ansible - https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html + +### Step 1: Clone the Github Repo + +First we need to clone the repo: + +``` +git clone git@github.com:vectorizedio/deployment-automation.git +``` + +Then change into the directory: + +``` +cd deployment-automation +``` + +You will want install the required roles needed by Ansible with the following +command: + +``` +ansible-galaxy install -r ansible/requirements.yml +``` + +### Step 2: Configure the hosts.ini file + +In the deployment-automation directory you will find a file called `hosts.ini`. +It will look something like: + +``` +[redpanda] +ip ansible_user=ssh_user ansible_become=True private_ip=pip id=0 +ip ansible_user=ssh_user ansible_become=True private_ip=pip id=1 + +[monitor] +ip ansible_user=ssh_user ansible_become=True private_ip=pip id=1 +``` + +Under the `[redpanda]` section, you will want to replace the following: + +- `ip` - the public ip address of the machine +- `ansible_user` - the username for ansible to use to ssh to the machine +- `private_ip` - the private ip address of the machine, could be the same as the public ip address +- `id` - The node id of the Redpanda instance, this needs to be unique for each host + +The `[monitor]` section is if you wish to have Prometheus and Grafana installed +on a give host. If you wish to not have this deployed then remove the +`[monitor]` section. + +### Step 3: Run the Ansible Playbook + +You can now setup Redpanda on your selected nodes by running the following +command: + +``` +ansible-playbook --private-key -i hosts.ini -v ansible/playbooks/provision-node.yml +``` + +Once this completes you will have a fully running cluster. + +## Manual Installation + +### Step 1: Install the Binary + +On Fedora/RedHat Systems: + +``` +curl -1sLf 'https://packages.vectorized.io/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | sudo -E bash && sudo yum install redpanda -y +``` + +On Debian Systems: + +``` +curl -1sLf 'https://packages.vectorized.io/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | sudo -E bash && sudo apt install redpanda -y +``` + +### Step 2: Set Redpanda Production Mode + +By default Redpanda is installed in **Development** mode, to we next need to +set Redpanda to run in **Production** mode. This is done with: + +``` +sudo rpk mode production +``` + +We then need to tune the hardware, which can be done by running the following +on each node: + +``` +sudo rpk tune all +``` + +> **_Optional: Benchmark your SSD_** +> +> On taller machines we recommend benchmarking your SSD. This can be done +> with `rpk iotune`. You only need to run this once. For reference, a decent +> local NVMe SSD should yield around 1GB/s sustained writes. +> `rpk iotune` will capture SSD wear and tear and give accurate measurements +> of what your hardware is actually capable of delivering. It is recommended +> you run this before benchmarking. +> +>If you are on AWS, GCP or Azure, creating a new instance and upgrading to +>an image with a recent Linux Kernel version is often the easiest way to +>work around bad devices. +> +>``` +>sudo rpk iotune # takes 10mins +>``` + +### Step 3: Configure and Start the Root Node + +Now that the software is installed we need to configure it. The first step is +to setup the root node. The root node will start as a standalone node, and +every other one will join it, forming a cluster along the way. + +For the root node we’ll choose 0 as its ID. --self tells the node which interface address to bind to. Usually you want that to be its private IP. + +``` +sudo rpk config bootstrap --id 0 --self && \ +sudo systemctl start redpanda-tuner redpanda +``` + +### Step 4: Configure and Start the Rest of the Nodes + +For every other node, we just have to choose a unique integer id for it and let +it know where to reach the root node. + +``` +sudo rpk config bootstrap --id \ +--self \ +--ips && \ +sudo systemctl start redpanda-tuner redpanda +``` + +### Step 5: Verify Installation + +You can verify that the cluster is up and running by checking the logs: + +``` +journalctl -u redpanda +``` + +You should also be able to create a topic with the following command: + +``` +rpk api topic create panda +``` \ No newline at end of file diff --git a/docs/www/quick-start-docker.md b/docs/www/quick-start-docker.md new file mode 100644 index 000000000000..7d7b783668e8 --- /dev/null +++ b/docs/www/quick-start-docker.md @@ -0,0 +1,158 @@ +--- +title: Docker Quick Start Guide +order: 0 +--- +# Docker Quick Start Guide + +Redpanda is a modern streaming platform for mission critical workloads. +Redpanda is also fully API compatible Kafka allowing you to make full use +of the Kafka ecosystem. + +This quick start guide to intended to help you get started with Redpanda +for development and testing purposes. For production deployments or +performance testing please see our +[Production Deployment](production-deployment.md) for more information. + +## Step 1: Create a bridge network + +The bridge network will allow for the Redpanda instances to communicate +with one another but still allow for the Kafka API to be availbale on +the localhost. + +``` +docker network create -d bridge redpandanet +``` + +## Step 2: Start Redpanda + +First we need to create the persistent volumes to be used by the Redpanda +instances. This will allow for us to be able to + +``` +docker volume create redpanda1; +docker volume create redpanda2; +docker volume create redpanda3; +``` + +We then need to start the first node of the Redpanda cluster. + +``` +docker run -d \ +--name=redpanda-1 \ +--hostname=redpanda-1 \ +--net=redpandanet \ +-p 9092:9092 \ +-v "redpanda1:/var/lib/redpanda/data" \ +vectorized/redpanda:v20.12.9 start \ +--smp 1 \ +--memory 1G \ +--reserve-memory 0M \ +--overprovisioned \ +--node-id 0 \ +--check=false \ +--kafka-addr 0.0.0.0:9092 \ +--advertise-kafka-addr 127.0.0.1:9092 \ +--rpc-addr 0.0.0.0:33145 \ +--advertise-rpc-addr redpanda-1:33145 +``` + +We then need to bring up the second and third node of the Redpanda cluster. + +``` +docker run -d \ +--name=redpanda-2 \ +--hostname=redpanda-2 \ +--net=redpandanet \ +-p 9093:9093 \ +-v "redpanda2:/var/lib/redpanda/data" \ +vectorized/redpanda:v20.12.9 start \ +--smp 1 \ +--memory 1G \ +--reserve-memory 0M \ +--overprovisioned \ +--node-id 1 \ +--seeds "redpanda-1:33145+0" \ +--check=false \ +--kafka-addr 0.0.0.0:9093 \ +--advertise-kafka-addr 127.0.0.1:9093 \ +--rpc-addr 0.0.0.0:33146 \ +--advertise-rpc-addr redpanda-2:33146 +``` + +``` +docker run -d \ +--name=redpanda-3 \ +--hostname=redpanda-3 \ +--net=redpandanet \ +-p 9094:9094 \ +-v "redpanda3:/var/lib/redpanda/data" \ +vectorized/redpanda:v20.12.9 start \ +--smp 1 \ +--memory 1G \ +--reserve-memory 0M \ +--overprovisioned \ +--node-id 2 \ +--seeds "redpanda-1:33145+0" \ +--check=false \ +--kafka-addr 0.0.0.0:9094 \ +--advertise-kafka-addr 127.0.0.1:9094 \ +--rpc-addr 0.0.0.0:33147 \ +--advertise-rpc-addr redpanda-3:33147 +``` + +## Using RPK + +Now you can run `rpk` on one of the containers to interact with the cluster: + +``` +docker exec -it redpanda-1 rpk api status +``` + +You should see output similar to the following: + +``` + Redpanda Cluster Status + + 0 (127.0.0.1:9092) (No partitions) + 1 (127.0.0.1:9093) (No partitions) + 2 (127.0.0.1:9094) (No partitions) +``` + +From here you can create topics: + +``` +docker exec -it redpanda-1 rpk api topic create panda +``` + +Then send some data to the topic: + +``` +docker exec -it redpanda-1 rpk api produce panda +``` + +You will be prompted to enter in some text and then hit `CTRL + D` to send. +Once you've sent a message you can then consume the message: + +``` +docker exec -it redpanda-1 rpk api consume panda +``` + +## Clean Up + +When you are finished with the cluster you can shutdown with the following +commands: + +``` +docker stop redpanda-1 redpanda-2 redpanda-3 +``` + +``` +docker rm redpanda-1 redpanda-2 redpanda-3 +``` + +If you wish to remove all the data that was stored in the cluster, you +can also delete the volumes: + +``` +docker volume rm redpanda1 redpanda2 redpanda3 +``` \ No newline at end of file diff --git a/docs/www/quick-start-kubernetes.md b/docs/www/quick-start-kubernetes.md new file mode 100644 index 000000000000..1f81eaa86bd8 --- /dev/null +++ b/docs/www/quick-start-kubernetes.md @@ -0,0 +1,94 @@ +--- +title: Kubernetes Quick Start Guide +order: 0 +--- +# Kubernetes Quick Start Guide + +Redpanda is a modern streaming platform for mission critical workloads. +Redpanda is also fully API compatible Kafka allowing you to make full +use of the Kafka ecosystem. + +This quick start guide to intended to help you get started with Redpanda for +development and testing purposes. For production deployments or performance +testing please see our [Production Deployment](production-deployment.md) for more information. + +Using [Helm](https://helm.sh/) is the fastest way to get started with Redpanda +on Kubernetes. First, we need to create a cluster. There are a number of +different ways to create a cluster, either local or with a hosting provider. + +- [Kind](#Kind) +- [AWS EKS](#AWS-EKS) +- [Google GKE](#Google-GKE) + +## Using Helm to Install Redpanda + +[Helm](https://helm.sh/) provides a quick and easy way to deploy Redpanda on +Kubernetes. To get started please use the +[Helm Quickstart Guide](https://helm.sh/docs/intro/quickstart/) +to install Helm. Once installed you will want to add the Redpanda chart repo. + +``` +helm repo add redpanda https://charts.vectorized.io/ +``` + +After the repo has been added, run the Helm repo update command to retrieve the +latest version of the Helm chart. + +``` +helm repo update +``` + +Now you can install Redpanda on your Kubernetes cluster using Helm. + +``` +helm install --namespace redpanda --create-namespace redpanda redpanda/redpanda +``` + +> **_Note:_** In order to communicate with the Redpanda cluster you will have to +> run a container inside the Kubernetes cluster. Currently a Load Balancer is +> not automatically created during deployment by default. + +## Kind + +[Kind](https://kind.sigs.k8s.io) is an easy to use tool for creating local Kubernetes clusters using Docker. Once you have Kind installed, setting up a cluster is a simple as: + +``` +kind create cluster +``` + +Once the cluster is created please follow the [Helm install instructions](#Using-Helm-to-Install-Redpanda). + +## AWS EKS + +First complete all the steps describe in [EKS Getting Started](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html) +guide. This includes installing `eksctl` which is used to create and delete +clusters in EKS. + +Once `eksctl` is installed, you can then use it to create an EKS cluster: + +``` +eksctl create cluster \ +--name redpanda \ +--nodegroup-name standard-workers \ +--node-type m5.xlarge \ +--nodes 3 \ +--nodes-min 1 \ +--nodes-max 4 \ +--node-ami auto +``` + +This command will take 10-15 minutes to complete. Once it is completed then +follow the [Helm install instructions](#Using-Helm-to-Install-Redpanda). + +## Google GKE + +First complete the "Before You Begin" steps describe in +[Google Kubernetes Engine Quickstart](https://cloud.google.com/kubernetes-engine/docs/quickstart). +Once complete you can create a cluster using the following command: + +``` +gcloud container clusters create redpanda --machine-type n1-standard-4 +``` + +Once the command completes then follow the +[Helm install instructions](#Using-Helm-to-Install-Redpanda) \ No newline at end of file diff --git a/docs/www/quick-start-linux.md b/docs/www/quick-start-linux.md new file mode 100644 index 000000000000..573bd2649df9 --- /dev/null +++ b/docs/www/quick-start-linux.md @@ -0,0 +1,66 @@ +--- +title: Linux Quick Start Guide +order: 0 +--- +# Linux Quick Start Guide + +Redpanda is a modern streaming platform for mission critical workloads. Redpanda +is also fully API compatible Kafka allowing you to make full use of the Kafka ecosystem. + +This quick start guide to intended to help you get started with Redpanda for +development and testing purposes. For production deployments or performance +testing please see our [Production Deployment](production-deployment.md) +for more information. + +## Installation + +The first step is to install either the RPM or DEB package of Redpanda. + +### On Fedora/RedHat Systems + +``` +curl -1sLf 'https://packages.vectorized.io/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | sudo -E bash && sudo yum install redpanda -y && sudo systemctl start redpanda +``` + +### On Debian Systems + +``` +curl -1sLf 'https://packages.vectorized.io/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | sudo -E bash && sudo apt install redpanda -y && sudo systemctl start redpanda +``` + +## Getting Started + +Now that Redpanda is installed we can either setup a single node cluster of +Redpanda or setup a local multi-node cluster using docker. + +### Single Node Deployment + +First we need to start Redpanda. + +``` +sudo systemctl start redpanda +``` + +Then we can check the status of the node with the following command: + +``` +sudo systemctl status redpanda +``` + +The output should look like the following: + +``` +● redpanda.service - Redpanda, the fastest queue in the West. + Loaded: loaded (/lib/systemd/system/redpanda.service; enabled; vendor preset: enabled) + Active: active (running) since Wed 2020-12-02 16:01:03 PST; 18s ago +``` + +You now have a running Redpanda instance! + +### Local Multi Node Deployment + +The simplest way to get a multi node cluster up and running is by using +`rpk container`. You can follow the +[rpk Container Guide](rpk-container-guide.md). If you want a more manual +approach you can check out the +[Quick Start Docker Guide](quick-start-docker.md). diff --git a/docs/www/quick-start-macos.md b/docs/www/quick-start-macos.md new file mode 100644 index 000000000000..ba22a8e71cf0 --- /dev/null +++ b/docs/www/quick-start-macos.md @@ -0,0 +1,45 @@ +--- +title: MacOS Quick Start Guide +order: 0 +--- +# MacOS Quick Start Guide + +Redpanda is a modern streaming platform for mission critical workloads. Redpanda +is also fully API compatible Kafka allowing you to make full use of the +Kafka ecosystem. + +This quick start guide to intended to help you get started with Redpanda +for development and testing purposes. For production deployments or +performance testing please see our +[Production Deployment](production-deployment.md) for more information. + +## Installation + +Redpanda itself cannot be run directly on MacOS, so we must make use of +docker to run Redpanda on MacOS. If you wish to run Redpanda directly +from docker please follow our +[Docker Quick Start Guide](quick-start-docker.md). Otherwise you can +download our binary, rpk, which stands for Redpanda Keeper, to orchestrate +the running of Redpanda via Docker for you. + +To install RPK, you can choose to either use [Homebrew](https://brew.sh/) +or download the binary directly. + +### Homebrew + +The fastest way to install on MacOS is to use Homebrew. If you have +Homebrew installed you can simply run the following command: + +``` +brew install vectorizedio/tap/redpanda +``` + +### Binary + +The latest RPK binary can be found here: [rpk-darwin-amd64.zip](https://github.com/vectorizedio/redpanda/releases/download/latest/rpk-darwin-amd64.zip) + +### Next Steps + +Now that you have RPK downloaded and installed you can check out our +[RPK Container Guide] which will take you through how to set up a +local development cluster. diff --git a/docs/www/rpk-container-guide.md b/docs/www/rpk-container-guide.md new file mode 100644 index 000000000000..424103c14d29 --- /dev/null +++ b/docs/www/rpk-container-guide.md @@ -0,0 +1,64 @@ +--- +title: rpk Container Guide +order: 0 +--- +# rpk Container Guide + +`rpk container` is a simple and quick way to stand up a local multi node cluster +for testing. `rpk container` leverages Docker. If you haven't done so already, +please follow the installation instructions for +[Docker](https://docs.docker.com/engine/install/) (Linux users) or +[Docker Desktop for Mac](https://www.docker.com/products/docker-desktop) +(MacOS users). + +It's important to note, however, that you won't need to interact with Docker directly or have experience with it. + +To get started, run `rpk container start -n 3`. This will start a 3-node cluster. You should see something like this (the addresses may vary): + +> `rpk container start` will take a minute the first time you run it, since it will download the latest stable version of Redpanda. The next time you run it it should be quicker. + +``` +Downloading latest version of Redpanda +Starting cluster + NODE ID ADDRESS + 0 172.24.1.2:58754 + 2 172.24.1.4:58756 + 1 172.24.1.3:58757 + +Cluster started! You may use 'rpk api' to interact with the cluster. E.g: + +rpk api status +``` + +It says we can check our cluster with `rpk api status` Let's try that! + +``` + Redpanda Cluster Status + + 0 (127.0.0.1:58754) (No partitions) + 1 (127.0.0.1:58757) (No partitions) + 2 (127.0.0.1:58756) (No partitions) +``` + +You can now connect your Kafka compatible applications directly to Redpanda +by using the ports listed above. In this example the ports to use would be +58754, 58757, 58756. + +All of the `rpk api` subcommands will detect the local cluster and use its addresses, so you don't have to configure anything or keep track of IPs and ports. + +For example, you can run `rpk api topic create` and it will work! + +``` +$ rpk api topic create -p 6 -r 3 new-topic +Created topic 'new-topic'. Partitions: 6, replicas: 3, cleanup policy: 'delete' +``` + +You can also stop the cluster using: + +``` +rpk container stop +``` + +You are all set! You can now use Redpanda to test your favorite Kafka +compatiable application or use the `rpk api` commands to further interace with +the local cluster!