Added kraft documentation

Author: amuraru

config/_default/config.toml

@@ -55,7 +55,7 @@ weight = 1
   project_name = "Koperator"
   product_name = "Koperator"
 
-  latest_version = "0.28.0-adobe-20250921" # Used in some installation commands
+  latest_version = "0.28.0-adobe-20250923" # Used in some installation commands
 
   ###############################################################################
   # Docsy-theme specific config customizations
@@ -69,7 +69,7 @@ weight = 1
   # The version number for the version of the docs represented in this doc set.
   # Used in the "version-banner" partial to display a version number for the
   # current doc set.
-  version = "0.28.0-adobe-20250921"
+  version = "0.28.0-adobe-20250923"
   version_menu_canonicallinks = true
 
   # A link to latest version of the docs. Used in the "version-banner" partial to

content/docs/_index.md

@@ -11,6 +11,7 @@ The Koperator (formerly called Banzai Cloud Kafka Operator) is a Kubernetes oper
 [Apache Kafka](https://kafka.apache.org) is an open-source distributed streaming platform, and some of the main features of the **Koperator** are:
 
 - the provisioning of secure and production-ready Kafka clusters
+- **KRaft mode support** for ZooKeeper-free Kafka deployments
 - **fine grained** broker configuration support
 - advanced and highly configurable External Access via LoadBalancers using **Envoy**
 - graceful Kafka cluster **scaling and rebalancing**
@@ -124,6 +125,18 @@ Read-only config requires broker restart to update all the others may be updated
 Operator CRD distinguishes these fields, and proceed with the right action. It can be a rolling upgrade, or
 a dynamic reconfiguration.
 
+### KRaft Mode Support (ZooKeeper-free Kafka)
+
+Koperator supports Apache Kafka's KRaft mode, which eliminates the dependency on ZooKeeper:
+
+- **Simplified Architecture**: Deploy Kafka clusters without requiring a separate ZooKeeper cluster
+- **Better Scalability**: Improved metadata handling for large-scale deployments
+- **Future-Ready**: KRaft is the future of Kafka and the recommended approach for new deployments
+- **Flexible Node Roles**: Support for dedicated controller nodes, broker nodes, or combined roles
+- **Production Ready**: Full support for SSL, monitoring, and all Koperator features in KRaft mode with Kafka 3.9.1
+
+For detailed KRaft configuration and deployment guides, see the [KRaft Mode Documentation]({{< relref "kraft.md" >}}).
+
 ### Seamless Istio mesh support
 
 - **Standard Istio Integration**: Koperator now uses standard Istio resources (Gateway, VirtualService) instead of deprecated banzaicloud istio-operator

content/docs/benchmarks/_index.md

@@ -74,12 +74,15 @@ How to setup the environment for the Kafka Performance Test.
 1. Install the Koperator CustomResourceDefinition resources (adjust the version number to the Koperator release you want to install) and the corresponding version of Koperator, the Operator for managing Apache Kafka on Kubernetes.
 
     ```bash
-    kubectl create --validate=false -f https://github.com/adobe/koperator/releases/download/v{{< param "latest_version" >}}/kafka-operator.crds.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_cruisecontroloperations.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkaclusters.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkatopics.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkausers.yaml
     ```
 
     ```bash
     helm install kafka-operator \
-    oci://ghcr.io/adobe/koperator/kafka-operator \
+    oci://ghcr.io/adobe/helm-charts/kafka-operator \
     --namespace=kafka \
     --create-namespace
     ```

content/docs/compatibility-matrix.md

@@ -13,7 +13,7 @@ This page shows you the list of supported Koperator versions, and the versions o
 
 |Image|Go version|
 |-|-|
-|ghcr.io/adobe/koperator/kafka-operator:0.28.0-adobe-20250921|1.25|
+|ghcr.io/adobe/koperator/kafka-operator:0.28.0-adobe-20250923|1.25|
 
 ## Available Apache Kafka images
 

content/docs/configurations/examples/_index.md

@@ -78,3 +78,11 @@ You can set node [affinity](https://kubernetes.io/docs/concepts/scheduling-evict
 You can configure your brokers to use custom [storage classes](https://kubernetes.io/docs/concepts/storage/storage-classes/).
 
 - [Custom storage class](https://github.com/adobe/koperator/blob/master/config/samples/simplekafkacluster_ebs_csi.yaml)
+
+## Kafka cluster with KRaft mode (ZooKeeper-free)
+
+You can deploy Kafka clusters using KRaft mode, which eliminates the need for ZooKeeper by using Kafka's built-in consensus mechanism. This is the future of Kafka and is recommended for new deployments.
+
+- [Simple KafkaCluster with KRaft mode](https://github.com/adobe/koperator/blob/master/config/samples/kraft/simplekafkacluster_kraft.yaml)
+
+For detailed information about KRaft configuration and deployment, see {{% xref "../../kraft.md" %}}.

content/docs/create-kraft-cluster.sample

@@ -0,0 +1,77 @@
+kubectl create -n kafka -f - <<EOF
+apiVersion: kafka.banzaicloud.io/v1beta1
+kind: KafkaCluster
+metadata:
+  name: kafka-kraft
+spec:
+  kRaft: true
+  headlessServiceEnabled: true
+  clusterImage: "ghcr.io/adobe/koperator/kafka:2.13-3.9.1"
+  
+  brokerConfigGroups:
+    default:
+      storageConfigs:
+        - mountPath: "/kafka-logs"
+          pvcSpec:
+            accessModes:
+              - ReadWriteOnce
+            resources:
+              requests:
+                storage: 10Gi
+    broker:
+      processRoles:
+        - broker
+      storageConfigs:
+        - mountPath: "/kafka-logs-broker"
+          pvcSpec:
+            accessModes:
+              - ReadWriteOnce
+            resources:
+              requests:
+                storage: 10Gi
+
+  brokers:
+    # Broker-only nodes
+    - id: 0
+      brokerConfigGroup: "broker"
+    - id: 1
+      brokerConfigGroup: "broker"
+    - id: 2
+      brokerConfigGroup: "broker"
+    
+    # Controller-only nodes
+    - id: 3
+      brokerConfigGroup: "default"
+      brokerConfig:
+        processRoles:
+          - controller
+    - id: 4
+      brokerConfigGroup: "default"
+      brokerConfig:
+        processRoles:
+          - controller
+    - id: 5
+      brokerConfigGroup: "default"
+      brokerConfig:
+        processRoles:
+          - controller
+
+  listenersConfig:
+    internalListeners:
+      - type: "plaintext"
+        name: "internal"
+        containerPort: 29092
+        usedForInnerBrokerCommunication: true
+      - type: "plaintext"
+        name: "controller"
+        containerPort: 29093
+        usedForInnerBrokerCommunication: false
+        usedForControllerCommunication: true
+
+  cruiseControlConfig:
+    cruiseControlTaskSpec:
+      RetryDurationMinutes: 5
+    topicConfig:
+      partitions: 12
+      replicationFactor: 3
+EOF

content/docs/delete-kafka-operator.md

@@ -75,7 +75,10 @@ In case you want to delete the Koperator from your cluster, note that because of
 
 1. Delete Koperator Custom Resource Definitions (CRDs).
     ```
-    kubectl delete -f https://github.com/adobe/koperator/releases/download/v{{< param "latest_version" >}}/kafka-operator.crds.yaml
+    kubectl delete -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_cruisecontroloperations.yaml
+    kubectl delete -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkaclusters.yaml
+    kubectl delete -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkatopics.yaml
+    kubectl delete -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkausers.yaml
     ```
 
 ## Uninstall Prometheus operator

content/docs/install-kafka-operator.md

@@ -18,7 +18,7 @@ The operator installs version 3.9.1 of Apache Kafka, and can run on:
 
 - A Kubernetes cluster (minimum 6 vCPU and 10 GB RAM). Red Hat OpenShift is also supported in Koperator version 0.24 and newer, but note that it needs some permissions for certain components to function.
 
-> We believe in the `separation of concerns` principle, thus the Koperator does not install nor manage Apache ZooKeeper or cert-manager.
+> We believe in the `separation of concerns` principle, thus the Koperator does not install nor manage Apache ZooKeeper or cert-manager. Note that ZooKeeper is only required for traditional Kafka deployments - KRaft mode deployments do not require ZooKeeper.
 
 ## Install Koperator and its requirements independently {#install-kafka-operator-and-its-requirements-independently}
 
@@ -195,12 +195,14 @@ Koperator uses [cert-manager](https://cert-manager.io) for issuing certificates
     cert-manager-webhook-56889bfc96-x8szj      1/1     Running   0          117s
     ```
 
-### Install zookeeper-operator with Helm {#install-zookeeper-operator-with-helm}
+### Install zookeeper-operator with Helm (Optional for KRaft mode) {#install-zookeeper-operator-with-helm}
 
-Koperator requires [Apache Zookeeper](https://zookeeper.apache.org) for Kafka operations. You must:
+Koperator can use either [Apache Zookeeper](https://zookeeper.apache.org) or KRaft mode for Kafka cluster coordination:
 
-- Deploy zookeeper-operator if your environment doesn't have an instance of it yet.
-- Create a Zookeeper cluster if there is none in your environment yet for your Kafka cluster.
+- **For traditional deployments**: Deploy zookeeper-operator if your environment doesn't have an instance of it yet, and create a Zookeeper cluster if there is none in your environment yet for your Kafka cluster.
+- **For KRaft mode deployments**: ZooKeeper is not required. Skip this section and see {{% xref "/docs/kraft.md" %}} for KRaft configuration.
+
+If you're deploying a traditional Kafka cluster (non-KRaft), you must:
 
 > Note: You are recommended to create a separate ZooKeeper deployment for each Kafka cluster. If you want to share the same ZooKeeper cluster across multiple Kafka cluster instances, use a unique zk path in the KafkaCluster CR to avoid conflicts (even with previous defunct KafkaCluster instances).
 
@@ -489,9 +491,10 @@ Koperator can be deployed using its [Helm chart](https://github.com/adobe/kopera
 1. Install the Koperator CustomResourceDefinition resources (adjust the version number to the Koperator release you want to install). This is performed in a separate step to allow you to uninstall and reinstall Koperator without deleting your installed custom resources.
 
     ```bash
-    kubectl create \
-    --validate=false \
-    -f https://github.com/adobe/koperator/releases/download/v{{< param "latest_version" >}}/kafka-operator.crds.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_cruisecontroloperations.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkaclusters.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkatopics.yaml
+    kubectl apply -f https://raw.githubusercontent.com/adobe/koperator/refs/heads/master/config/base/crds/kafka.banzaicloud.io_kafkausers.yaml
     ```
 
     Expected output:
@@ -537,17 +540,30 @@ Koperator can be deployed using its [Helm chart](https://github.com/adobe/kopera
         clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "system:serviceaccount:{NAMESPACE_FOR_KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT}:{KAFKA_CLUSTER_BROKER_SERVICE_ACCOUNT_NAME}"
         ```
 
-1. Install Koperator into the *kafka* namespace:
+1. Install Koperator into the *kafka* namespace using the OCI Helm chart from GitHub Container Registry:
+
+    > 📦 **View available versions**: [ghcr.io/adobe/koperator/kafka-operator](https://github.com/adobe/koperator/pkgs/container/koperator%2Fkafka-operator/versions)
 
     ```bash
-    helm install \
-    kafka-operator \
-    oci://ghcr.io/adobe/koperator/kafka-operator \
-    --version {{< param "latest_version" >}} \
-    --namespace=kafka \
-    --create-namespace \
-    --atomic \
-    --debug
+    # Install the latest release
+    helm install kafka-operator oci://ghcr.io/adobe/helm-charts/kafka-operator --namespace=kafka --create-namespace
+
+    # Or install a specific version (replace with desired version)
+    helm install kafka-operator oci://ghcr.io/adobe/helm-charts/kafka-operator --version {{< param "latest_version" >}} --namespace=kafka --create-namespace
+    ```
+
+    #### Pull and inspect the chart before installation
+
+    ```bash
+    # Pull the chart locally
+    helm pull oci://ghcr.io/adobe/helm-charts/kafka-operator --version {{< param "latest_version" >}}
+
+    # Extract and inspect
+    tar -xzf kafka-operator-{{< param "latest_version" >}}.tgz
+    helm template kafka-operator ./kafka-operator/
+
+    # Install from local chart
+    helm install kafka-operator ./kafka-operator/ --namespace=kafka --create-namespace
     ```
 
     Expected output:
@@ -602,6 +618,14 @@ Koperator can be deployed using its [Helm chart](https://github.com/adobe/kopera
         -f https://raw.githubusercontent.com/adobe/koperator/v{{< param "latest_version" >}}/config/samples/simplekafkacluster_ssl.yaml
         ```
 
+    - To create a sample Kafka cluster using KRaft mode (ZooKeeper-free), run the following command. For details on KRaft configuration, see {{% xref "/docs/kraft.md" %}}.
+
+        ```bash
+        kubectl create \
+        -n kafka \
+        -f https://raw.githubusercontent.com/adobe/koperator/master/config/samples/kraft/simplekafkacluster_kraft.yaml
+        ```
+
     Expected output:
 
     ```bash