Manage Redpanda in Kubernetes
Customize the values of the Redpanda Helm chart or Redpanda resource to configure both the Redpanda cluster and the Kubernetes components.
Customize the values of the Redpanda Helm chart or Redpanda resource to configure both the Redpanda cluster and the Kubernetes components.
Use the Topic resource to declaratively create Kafka topics as part of a Redpanda deployment. Each Topic resource is mapped to a topic in your Redpanda cluster. The topic controller keeps the corresponding Kafka topic in sync with the Topic resource.
Configure Cloud Topics on Kubernetes to optimize for latency-tolerant, high-throughput workloads using object storage as the primary data tier.
Learn how to create and manage connectors using Redpanda Console or the Kafka Connect REST API.
Find information about Redpanda storage in Kubernetes.
Tiered Storage helps to lower storage costs by offloading log segments to object storage.
Learn how to set up and manage network connections for Redpanda in Kubernetes. This section covers a range of topics, including how to enable external access, connect clients to a Redpanda cluster, and configure listeners.
Learn what options are available for securing Redpanda clusters, including TLS encryption, authentication, authorization, and audit logging.
Enable rack awareness to place partition replicas across different failure zones.
Create read-only topics (Remote Read Replica topics) that mirror topics on a different cluster.
Configure and manage shadow links for disaster recovery in Kubernetes deployments.
Configure your Pod resources such as memory, CPU, and storage.
Learn how to scale a Redpanda cluster vertically to increase its resources and horizontally to add or remove brokers from a cluster.
Manage the lifecycle of Redpanda brokers in Kubernetes, including node pools, decommissioning, recovery mode, and rolling restarts.
Find topics about how to monitor Redpanda deployments in Kubernetes.
With resilience testing, you can introduce failures and observe how the system behaves under each failure scenario.