DO NOT MERGE: Supertubes rebranding

docs/_index.md

@@ -1,17 +1,18 @@
 ---
-title: Kafka operator
-img: /docs/supertubes/kafka-operator/img/kafka-operator-arch.png
+title: Koperator
+img: /docs/kafka-operator/img/kafka-operator-arch.png
 weight: 700
 cascade:
   module: kafka-operator
-  githubEditUrl: "https://github.com/banzaicloud/kafka-operator-docs/edit/master/docs/"
+  githubEditUrl: "https://github.com/banzaicloud/koperator-docs/edit/master/docs/"
+  operatorName: "Koperator"
 ---
 
-The Banzai Cloud Kafka operator is a Kubernetes operator to automate provisioning, management, autoscaling and operations of [Apache Kafka](https://kafka.apache.org) clusters deployed to K8s.
+The {{< kafka-operator >}} (formerly called Banzai Cloud Kafka Operator) is a Kubernetes operator to automate provisioning, management, autoscaling and operations of [Apache Kafka](https://kafka.apache.org) clusters deployed to K8s.
 
 ## Overview
 
-[Apache Kafka](https://kafka.apache.org) is an open-source distributed streaming platform, and some of the main features of the **Kafka-operator** are:
+[Apache Kafka](https://kafka.apache.org) is an open-source distributed streaming platform, and some of the main features of the **{{< kafka-operator >}}** are:
 
 - the provisioning of secure and production-ready Kafka clusters
 - **fine grained** broker configuration support
@@ -23,17 +24,21 @@ The Banzai Cloud Kafka operator is a Kubernetes operator to automate provisionin
 - graceful rolling upgrade
 - advanced topic and user management via CRD
 
-![Kafka-operator architecture](./img/kafka-operator-arch.png)
+![{{< kafka-operator >}} architecture](./img/kafka-operator-arch.png)
 
->We took a different approach to what's out there - we believe for a good reason - please read on to understand more about our [design motivations](features/) and some of the [scenarios](scenarios/) which were driving us to create the Banzai Cloud Kafka operator.
 
-{{% include-headless "doc/kafka-operator-supertubes-intro.md" %}}
+>We took a different approach to what's out there - we believe for a good reason - please read on to understand more about our [design motivations](features/) and some of the [scenarios](scenarios/) which drove us to create the {{< kafka-operator >}}.
+
+{{% include-headless "kafka-operator-supertubes-intro.md" %}}
 
 ## Motivation
 
-At [Banzai Cloud](https://banzaicloud.com) we are building a Kubernetes distribution, [PKE](/products/pke/), and a hybrid-cloud container management platform, [Pipeline](/products/pipeline/), that operate Kafka clusters (among other types) for our customers. Apache Kafka predates Kubernetes and was designed mostly for `static` on-premise environments. State management, node identity, failover, etc all come part and parcel with Kafka, so making it work properly on Kubernetes and on an underlying dynamic environment can be a challenge.
+Apache Kafka predates Kubernetes and was designed mostly for `static` on-premise environments. State management, node identity, failover, etc all come part and parcel with Kafka, so making it work properly on Kubernetes and on an underlying dynamic environment can be a challenge.
+
+There are already several approaches to operating Apache Kafka on Kubernetes, however, we did not find them appropriate for use in a highly dynamic environment, nor capable of meeting our customers' needs. At the same time, there is substantial interest within the Kafka community for a solution which enables Kafka on Kubernetes, both in the open source and closed source space.
+>We took a different approach to what's out there - we believe for a good reason - please read on to understand more about our [design motivations](features/) and some of the [scenarios](scenarios/) which were driving us to create the {{< kafka-operator >}}.
 
-There are already several approaches to operating Kafka on Kubernetes, however, we did not find them appropriate for use in a highly dynamic environment, nor capable of meeting our customers' needs. At the same time, there is substantial interest within the Kafka community for a solution which enables Kafka on Kubernetes, both in the open source and closed source space.
->We took a different approach to what's out there - we believe for a good reason - please read on to understand more about our [design motivations](features/) and some of the [scenarios](scenarios/) which were driving us to create the Banzai Cloud Kafka operator.
+Finally, our motivation is to build an open source solution and a community which drives the innovation and features of this operator. We are long-term contributors and active community members of both Apache Kafka and Kubernetes, and we hope to recreate a similar community around this operator.
 
-Finally, our motivation is to build an open source solution and a community which drives the innovation and features of this operator. We are long term contributors and active community members of both Apache Kafka and Kubernetes, and we hope to recreate a similar community around this operator.
+---
+Apache Kafka, Kafka, and the Kafka logo are either registered trademarks or trademarks of The Apache Software Foundation in the United States and other countries.

docs/benchmarks/_index.md

@@ -20,20 +20,20 @@ banzai login
     1. Save the used route table id on the generated subnet
     1. Create two additional subnet in the VPC (choose different Availability Zones)
 
-      - Modify your newly created subnet Auto Assign IP setting
-      - Enable auto-assign public IPV4 address
+        - Modify your newly created subnet Auto Assign IP setting
+        - Enable auto-assign public IPV4 address
 
     1. Assign the saved route table id to the two additional subnets
 
-      - On Route Table page click Actions and Edit subnet associations
+        - On Route Table page click Actions and Edit subnet associations
 
 1. Create the cluster itself.
 
     ```bash
     banzai cluster create
     ```
 
-    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/kafka-operator/master/docs/benchmarks/infrastructure/cluster_pke.json)
+    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/koperator/master/docs/benchmarks/infrastructure/cluster_pke.json)
 
     > Please don't forget to fill out the template with the created ids.
 
@@ -63,7 +63,7 @@ banzai login
     banzai cluster create
     ```
 
-    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/kafka-operator/master/docs/benchmarks/infrastructure/cluster_gke.json)
+    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/koperator/master/docs/benchmarks/infrastructure/cluster_gke.json)
 
     > Please don't forget to fill out the template with the created ids.
 
@@ -90,7 +90,7 @@ banzai login
     banzai cluster create
     ```
 
-    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/kafka-operator/master/docs/benchmarks/infrastructure/cluster_eks.json)
+    The required cluster template file can be found [here](https://raw.githubusercontent.com/banzaicloud/koperator/master/docs/benchmarks/infrastructure/cluster_eks.json)
 
     > Please don't forget to fill out the template with the created ids.
 
@@ -131,13 +131,13 @@ banzai login
     EOF
     ```
 
-1. Install the latest version of Banzai Cloud Kafka Operator.
+1. Install the latest version of {{< kafka-operator >}}, the Operator for managing Apache Kafka on Kubernetes.
 
     ```bash
     helm install --name=kafka-operator banzaicloud-stable/kafka-operator
     ```
 
-1. Create a 3 broker Kafka Cluster using the [provided](https://raw.githubusercontent.com/banzaicloud/kafka-operator/master/docs/benchmarks/infrastructure/kafka.yaml) yaml.
+1. Create a 3 broker Kafka Cluster using the [provided](https://raw.githubusercontent.com/banzaicloud/koperator/master/docs/benchmarks/infrastructure/kafka.yaml) yaml.
 
     This will install 3 brokers partitioned to three different zone with fast ssd.
 1. Create a client container inside the cluster
@@ -169,16 +169,16 @@ banzai login
     ./opt/kafka/bin/kafka-topics.sh --zookeeper zookeeper-client.zookeeper:2181 --topic perftest3 --create --replication-factor 3 --partitions 3
     ```
 
-Monitoring environment automatically installed, find your cluster and Grafanas UI/credentials on our [UI](https://banzaicloud.com/pipeline/). To monitor the infrastructure we used the official Node Exporter dashboard available with id `1860`.
+Monitoring environment is automatically installed. To monitor the infrastructure we used the official Node Exporter dashboard available with id `1860`.
 
 ## Run the tests
 
-1. Run perf test against the cluster, by building the provided Docker [image](https://raw.githubusercontent.com/banzaicloud/kafka-operator/master/docs/benchmarks/loadgens/Dockerfile)
+1. Run perf test against the cluster, by building the provided Docker [image](https://raw.githubusercontent.com/banzaicloud/koperator/master/docs/benchmarks/loadgens/Dockerfile)
 
-```bash
-docker build -t yourname/perfload:0.1.0 /loadgens
-docker push yourname/perfload:0.1.0
-```
+    ```bash
+    docker build -t yourname/perfload:0.1.0 /loadgens
+    docker push yourname/perfload:0.1.0
+    ```
 
 1. Submit the perf test application:
 

docs/compatibility-matrix.md

@@ -4,43 +4,50 @@ shorttitle: Supported versions
 weight: 770
 ---
 
-This page shows you the list of supported Kafka operator versions, and the versions of other components they are compatible with.
+This page shows you the list of supported {{< kafka-operator >}} versions, and the versions of other components they are compatible with.
 
 ## Compatibility matrix
 
 |Operator Version|Apache Kafka Version|JMX Exporter Version|Cruise Control Version|Istio Operator Version|Example cluster CR|Maintained|
 |-------|------|----------------|-------|----|---|-|
-|v0.14.0|2.5.0+|0.14.0|2.5.23|1.5|[link](https://github.com/banzaicloud/kafka-operator/blob/v0.14.0/config/samples/simplekafkacluster.yaml)|+|
-|v0.15.0|2.5.0+|0.14.0|2.5.28|1.8|[link](https://github.com/banzaicloud/kafka-operator/blob/v0.15.1/config/samples/simplekafkacluster.yaml)|+|
-|v0.16.0|2.5.0+|0.15.0|2.5.37|1.9|[link](https://github.com/banzaicloud/kafka-operator/blob/v0.16.1/config/samples/simplekafkacluster.yaml)|+|
+|v0.18.3|2.6.2+|0.15.0|2.5.37|1.10|[link](https://github.com/banzaicloud/koperator/blob/v0.18.3/config/samples/simplekafkacluster.yaml)|-|
+|v0.19.0|2.6.2+|0.15.0|2.5.68|1.10|[link](https://github.com/banzaicloud/koperator/blob/v0.19.0/config/samples/simplekafkacluster.yaml)|-|
+|v0.20.0|2.6.2+|0.15.0|2.5.68|1.10|[link](https://github.com/banzaicloud/koperator/blob/v0.20.0/config/samples/simplekafkacluster.yaml)|-|
+|v0.20.2|2.6.2+|0.16.1|2.5.80|1.10|[link](https://github.com/banzaicloud/koperator/blob/v0.20.2/config/samples/simplekafkacluster.yaml)|+|
+|v0.21.0|2.6.2+|0.16.1|2.5.86|2.11|[link](https://github.com/banzaicloud/koperator/blob/v0.21.0/config/samples/simplekafkacluster.yaml)|+|
+|v0.21.1|2.6.2+|0.16.1|2.5.86|2.11|[link](https://github.com/banzaicloud/koperator/blob/v0.21.1/config/samples/simplekafkacluster.yaml)|+|
+|v0.21.2|2.6.2+|0.16.1|2.5.86|2.11|[link](https://github.com/banzaicloud/koperator/blob/v0.21.2/config/samples/simplekafkacluster.yaml)|+|
 
-## Available Kafka operator images
+## Available {{< kafka-operator >}} images
 
 |Image|Go version|
 |-|-|
-|ghcr.io/banzaicloud/kafka-operator:v0.14.0|1.14|
-|ghcr.io/banzaicloud/kafka-operator:v0.15.0|1.15|
-|ghcr.io/banzaicloud/kafka-operator:v0.15.1|1.15|
-|ghcr.io/banzaicloud/kafka-operator:v0.16.0|1.15|
-|ghcr.io/banzaicloud/kafka-operator:v0.16.1|1.15|
+|ghcr.io/banzaicloud/kafka-operator:v0.17.0|1.16|
+|ghcr.io/banzaicloud/kafka-operator:v0.18.3|1.16|
+|ghcr.io/banzaicloud/kafka-operator:v0.19.0 |1.16|
+|ghcr.io/banzaicloud/kafka-operator:v0.20.2 |1.17|
+|ghcr.io/banzaicloud/kafka-operator:v0.21.0 |1.17|
+|ghcr.io/banzaicloud/kafka-operator:v0.21.1 |1.17|
+|ghcr.io/banzaicloud/kafka-operator:v0.21.2 |1.17|
 
 ## Available Apache Kafka images
 
 |Image|Java version|
 |-|-|
-|banzaicloud/kafka:2.13-2.5.0-bzc.1|11|
-|banzaicloud/kafka:2.13-2.5.1-bzc.1|11|
-|ghcr.io/banzaicloud/kafka:2.13-2.6.0-bzc.1|11|
-|ghcr.io/banzaicloud/kafka:2.13-2.6.1-bzc.1|11|
+|ghcr.io/banzaicloud/kafka:2.13-2.6.2-bzc.1|11|
 |ghcr.io/banzaicloud/kafka:2.13-2.7.0-bzc.1|11|
 |ghcr.io/banzaicloud/kafka:2.13-2.7.0-bzc.2|11|
+|ghcr.io/banzaicloud/kafka:2.13-2.8.0|11|
+|ghcr.io/banzaicloud/kafka:2.13-2.8.1|11|
+|ghcr.io/banzaicloud/kafka:2.13-3.1.0|17|
 
 ## Available JMX Exporter images
 
 |Image|Java version|
 |-|-|
 |ghcr.io/banzaicloud/jmx-javaagent:0.14.0|11|
 |ghcr.io/banzaicloud/jmx-javaagent:0.15.0|11|
+|ghcr.io/banzaicloud/jmx-javaagent:0.16.1|11|
 
 ## Available Cruise Control images
 
@@ -51,3 +58,7 @@ This page shows you the list of supported Kafka operator versions, and the versi
 |ghcr.io/banzaicloud/cruise-control:2.5.34|11|
 |ghcr.io/banzaicloud/cruise-control:2.5.37|11|
 |ghcr.io/banzaicloud/cruise-control:2.5.43|11|
+|ghcr.io/banzaicloud/cruise-control:2.5.53|11|
+|ghcr.io/banzaicloud/cruise-control:2.5.68|11|
+|ghcr.io/banzaicloud/cruise-control:2.5.80|11|
+|ghcr.io/banzaicloud/cruise-control:2.5.86|11|

docs/create-topic.sample

@@ -9,4 +9,7 @@ spec:
     name: my-topic
     partitions: 1
     replicationFactor: 1
+    config:
+        "retention.ms": "604800000"
+        "cleanup.policy": "delete"
 EOF

docs/create-zookeeper.sample

@@ -5,5 +5,5 @@ metadata:
     name: zookeeper
     namespace: zookeeper
 spec:
-    replicas: 3
-EOF
+    replicas: 1
+EOF

docs/delete-kafka-operator.md

@@ -1,14 +1,14 @@
 ---
-title: Delete Kafka operator
+title: Delete the operator
 shorttitle: Delete operator
 weight: 950
 ---
 
-In case you want to delete the Kafka operator from your cluster, note that because of dependencies between the various components, they must be deleted in specific order.
+In case you want to delete {{< kafka-operator >}} from your cluster, note that because of dependencies between the various components, they must be deleted in specific order.
 
-{{< warning >}}It’s important to delete the kafka-operator deployment as the last step.
+{{< warning >}}It’s important to delete the {{< kafka-operator >}} deployment as the last step.
 {{< /warning >}}
 
 1. Delete the *KafkaCluster* custom resources that represent the Kafka cluster and Cruise Control.
-1. Wait until kafka-operator deletes all resources.  Note that KafkaCluster, KafkaTopic and KafkaUser custom resources are protected with kubernetes finalizers, so those won’t be actually deleted from Kubernetes until the kafka-operator removes those finalizers. After the kafka-operator has finished cleaning up everything, it removes the finalizers. In case you delete the kafka-operator deployment before it cleans up everything you need to remove the finalizers manually.
-1. Delete the kafka-operator deployment.
+1. Wait until {{< kafka-operator >}} deletes all resources. Note that KafkaCluster, KafkaTopic and KafkaUser custom resources are protected with Kubernetes finalizers, so those won’t be actually deleted from Kubernetes until the {{< kafka-operator >}} removes those finalizers. After the {{< kafka-operator >}} has finished cleaning up everything, it removes the finalizers. In case you delete the {{< kafka-operator >}} deployment before it cleans up everything, you need to remove the finalizers manually.
+1. Delete the {{< kafka-operator >}} deployment.

docs/developer.md

@@ -11,13 +11,13 @@ If you find this project useful here's how you can help:
 
 - Send a pull request with your new features and bug fixes
 - Help new users with issues they may encounter
-- Support the development of this project and [star this repo](https://github.com/banzaicloud/kafka-operator/)!
+- Support the development of this project and [star this repo](https://github.com/banzaicloud/koperator/)!
 
-When you are opening a PR to Kafka operator the first time we will require you to sign a standard CLA.
+When you are opening a PR to {{< kafka-operator >}} the first time we will require you to sign a standard CLA.
 
-## How to run Kafka-operator in your cluster with your changes
+## How to run {{< kafka-operator >}} in your cluster with your changes
 
-The Kafka operator is built on the [kubebuilder](https://github.com/kubernetes-sigs/kubebuilder) project.
+{{< kafka-operator >}} is built on the [kubebuilder](https://github.com/kubernetes-sigs/kubebuilder) project.
 
 To build the operator and run tests: