Botkube rebranding (#793)

* change BotKube -> Botkube

* change logos and images related to old brand

Author: madebyrogal

.github/CODEOWNERS

@@ -1,4 +1,4 @@
-# BotKube maintainers (email: [email protected])
+# Botkube maintainers (email: [email protected])
 # Maintainers are listed alphabetically
 
 * @kubeshop/botkube-dev @PrasadG193

.github/ISSUE_TEMPLATE/bug_report.md

@@ -13,7 +13,7 @@ labels: bug
 
 <!-- Provide a clear and concise description of the problem.
 Describe where it appears, when it occurred, and what it affects.
-Provide all relevant technical details such as the BotKube version. -->
+Provide all relevant technical details such as the Botkube version. -->
 
 ## Expected behavior
 

.github/workflows/branch-build.yml

@@ -78,7 +78,7 @@ jobs:
       - name: Create cluster
         run: "k3d cluster create botkube --wait --timeout=5m"
 
-      - name: Install BotKube
+      - name: Install Botkube
         env:
           SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
           DISCORD_BOT_TOKEN: ${{ secrets.DISCORD_BOT_TOKEN }}

.github/workflows/pr-build.yaml

@@ -11,7 +11,7 @@ on:
       - '.codespell-whitelist'
       - '.gitignore'
       - '.golangci.yml'
-      - 'botkube-title.jpg'
+      - 'botkube-title.png'
       - 'botkube_arch.jpg'
       - 'CODE_OF_CONDUCT.md'
       - 'comm_config.yaml.tpl'
@@ -34,7 +34,7 @@ env:
 jobs:
 
   save-image:
-    name: Build and save BotKube image
+    name: Build and save Botkube image
     runs-on: ubuntu-latest
 
     permissions:
@@ -71,7 +71,7 @@ jobs:
           retention-days: 1
 
   push-image:
-    name: Push BotKube image
+    name: Push Botkube image
     runs-on: ubuntu-latest
     needs: [save-image]
 
@@ -111,8 +111,8 @@ jobs:
         run: |
           cat > $GITHUB_STEP_SUMMARY << ENDOFFILE
 
-          ### BotKube image published successfully! :rocket:
-          To test BotKube with PR changes, run:
+          ### Botkube image published successfully! :rocket:
+          To test Botkube with PR changes, run:
 
               gh pr checkout ${PR_NUMBER}
               helm install botkube -n botkube --create-namespace \\
@@ -151,7 +151,7 @@ jobs:
       - name: Create cluster
         run: "k3d cluster create botkube --wait --timeout=5m"
 
-      - name: Install BotKube
+      - name: Install Botkube
         env:
           SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
           DISCORD_BOT_TOKEN: ${{ secrets.DISCORD_BOT_TOKEN }}

.github/workflows/process-chart.yml

@@ -95,7 +95,7 @@ jobs:
           cd ${{ github.workspace }}/chart
           helm repo index --url "${{ env.CHART_REPOSITORY }}" --merge ./index.yaml .
           git add .
-          git commit -m "${{ inputs.next-version }} BotKube Helm chart release"
+          git commit -m "${{ inputs.next-version }} Botkube Helm chart release"
           git push
         env:
           GITHUB_TOKEN: ${{ secrets.gh-token }}

CONTRIBUTING.md

@@ -1,26 +1,26 @@
-# How to Contribute to BotKube
+# How to Contribute to Botkube
 
 We'd love your help!
 
-BotKube is [MIT Licensed](LICENSE) and accepts contributions via GitHub pull requests. This document outlines conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contributions accepted.
+Botkube is [MIT Licensed](LICENSE) and accepts contributions via GitHub pull requests. This document outlines conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contributions accepted.
 
 We gratefully welcome improvements to [documentation](https://botkube.io/ "Go to documentation site") as well as to code.
 
 ## Contributing to documentation
 
 Follow the [botkube-docs/CONTRIBUTING.md](https://github.com/kubeshop/botkube-docs/blob/main/CONTRIBUTING.md) file to learn how to contribute to documentation.
 
-## Build and run BotKube from source code
+## Build and run Botkube from source code
 
-This section describes how to build and run the BotKube from the source code.
+This section describes how to build and run the Botkube from the source code.
 
 ### Prerequisite
 
 - [Go](https://go.dev), at least 1.18
 - `make`
 - [Docker](https://docs.docker.com/install/)
 - Kubernetes cluster, at least 1.21
-- Cloned BotKube repository
+- Cloned Botkube repository
 
    Use the following command to clone it:
    ```sh
@@ -29,11 +29,11 @@ This section describes how to build and run the BotKube from the source code.
 
 ### Build and install on Kubernetes
 
-1. Build BotKube and create a new container image tagged as `ghcr.io/kubeshop/botkube:v9.99.9-dev`. Choose one option:
+1. Build Botkube and create a new container image tagged as `ghcr.io/kubeshop/botkube:v9.99.9-dev`. Choose one option:
 
    - **Single target build for your local K8s cluster**
 
-     This is ideal for running BotKube on a local cluster, e.g. using [kind](https://kind.sigs.k8s.io) or [`minikube`](https://minikube.sigs.k8s.io/docs/).
+     This is ideal for running Botkube on a local cluster, e.g. using [kind](https://kind.sigs.k8s.io) or [`minikube`](https://minikube.sigs.k8s.io/docs/).
 
      Remember to set the `IMAGE_PLATFORM` env var to your target architecture. For example, the command below builds the `linux/arm64` target. By default, the build targets `linux/amd64`.
 
@@ -46,7 +46,7 @@ This section describes how to build and run the BotKube from the source code.
 
    - **Multi-arch target builds for any K8s cluster**
 
-     This is ideal for running BotKube on remote clusters.
+     This is ideal for running Botkube on remote clusters.
 
      When tagging your dev image take care to add your target image architecture as a suffix. For example, in the command below we added `-amd64` as our target architecture.
 
@@ -81,9 +81,9 @@ This section describes how to build and run the BotKube from the source code.
 
 ### Build and run locally
 
-For faster development, you can also build and run BotKube outside K8s cluster.
+For faster development, you can also build and run Botkube outside K8s cluster.
 
-1. Build BotKube local binary:
+1. Build Botkube local binary:
 
    ```sh
    # Fetch the dependencies
@@ -124,7 +124,7 @@ For faster development, you can also build and run BotKube outside K8s cluster.
    ...
    ```
 
-6. Run BotKube binary:
+6. Run Botkube binary:
 
    ```sh
    ./botkube
@@ -161,8 +161,8 @@ For faster development, you can also build and run BotKube outside K8s cluster.
 
 ## Support Channels
 
-Join the BotKube-related discussion on Slack!
+Join the Botkube-related discussion on Slack!
 
-Create your Slack account on [BotKube](https://join.botkube.io) workspace.
+Create your Slack account on [Botkube](https://join.botkube.io) workspace.
 
 To report bug or feature, use [GitHub issues](https://github.com/kubeshop/botkube/issues/new/choose).

README.md

@@ -1,9 +1,9 @@
 <p align="center">
-  <img src="./docs/assets/botkube-title.jpg" alt="BotKube Logo Light" width="90%" />
+  <img src="./docs/assets/botkube-title.png" alt="Botkube Logo Light" />
 </p>
 
 <p align="center">
-  BotKube is a messaging bot for monitoring and debugging Kubernetes clusters.
+  Botkube is a messaging bot for monitoring and debugging Kubernetes clusters.
 </p>
 
 
@@ -15,7 +15,7 @@
     <img src="https://img.shields.io/github/license/kubeshop/botkube" alt="License"/>
   </a>
   <a href="https://join.botkube.io/">
-    <img src="https://badgen.net/badge/slack/BotKube?icon=slack" alt="Slack" />
+    <img src="https://badgen.net/badge/slack/Botkube?icon=slack" alt="Slack" />
   </a>
   <a href="https://github.com/kubeshop/botkube/actions?query=workflow%3ACI+branch%3Amain">
     <img src="https://github.com/kubeshop/botkube/workflows/CI/badge.svg?branch=main" alt="CI Build" />
@@ -27,17 +27,17 @@
 
 ## Overview
 
-BotKube helps you monitor your Kubernetes cluster, debug critical deployments and gives recommendations for standard practices by running checks on the Kubernetes resources. It integrates with multiple communication platforms, such as [Slack](https://slack.com), [Discord](https://discord.com/), or [Mattermost](https://mattermost.com).
+Botkube helps you monitor your Kubernetes cluster, debug critical deployments and gives recommendations for standard practices by running checks on the Kubernetes resources. It integrates with multiple communication platforms, such as [Slack](https://slack.com), [Discord](https://discord.com/), or [Mattermost](https://mattermost.com).
 
-You can also execute `kubectl` commands on K8s cluster via BotKube which helps debugging an application or cluster.
+You can also execute `kubectl` commands on K8s cluster via Botkube which helps debugging an application or cluster.
 
 <p align="center">
 <img src="./docs/assets/main-demo.gif" />
 </p>
 
 ## Getting started
 
-Please follow [this](https://botkube.io/installation/) for a complete BotKube installation guide.
+Please follow [this](https://botkube.io/installation/) for a complete Botkube installation guide.
 
 ## Documentation
 
@@ -49,39 +49,39 @@ For full documentation, visit [botkube.io](https://botkube.io). The documentatio
 
 ### Execute `kubectl` commands
 
-The same `kubectl` capabilities inside your favorite communicator. You do not have to learn anything new! Plus, you can configure which `kubectl` commands BotKube can execute. See [configuration](https://botkube.io/configuration/resource/) for details.
+The same `kubectl` capabilities inside your favorite communicator. You do not have to learn anything new! Plus, you can configure which `kubectl` commands Botkube can execute. See [configuration](https://botkube.io/configuration/resource/) for details.
 
 <br /><br />
 
 <img src="./docs/assets/icons/question-answer-line.svg" width="10%" align="left"/>
 
 ### Use multiple communication platforms
 
-BotKube integrates with Slack, Discord, Mattermost, Microsoft Teams, ElasticSearch and outgoing webhook. See [configuration](https://botkube.io/configuration/communication/) syntax for details.
+Botkube integrates with Slack, Discord, Mattermost, Microsoft Teams, ElasticSearch and outgoing webhook. See [configuration](https://botkube.io/configuration/communication/) syntax for details.
 
 <br /><br />
 
 <img src="./docs/assets/icons/stack-line.svg" width="13%" align="right"/>
 
 ### Monitor any Kubernetes resource
 
-BotKube supports literally any Kubernetes resource, including Custom Resources. For example, if you use [`cert-manager`](https://cert-manager.io/), you can get alerted about certificate issue, or backup failure in case you use backup tools like [Velero](https://velero.io/) or [Kanister](https://kanister.io/).
+Botkube supports literally any Kubernetes resource, including Custom Resources. For example, if you use [`cert-manager`](https://cert-manager.io/), you can get alerted about certificate issue, or backup failure in case you use backup tools like [Velero](https://velero.io/) or [Kanister](https://kanister.io/).
 
 <br /><br />
 
 <img src="./docs/assets/icons/bug-line.svg" width="12%" align="left"/>
 
 ### Debug anywhere, anytime
 
-Using BotKube you can debug your apps deployed on Kubernetes from anywhere. To extract crucial information from the cluster, you can even use mobile communicator apps, like Slack. The entire team can see what steps have already been taken and avoid duplicated work.
+Using Botkube you can debug your apps deployed on Kubernetes from anywhere. To extract crucial information from the cluster, you can even use mobile communicator apps, like Slack. The entire team can see what steps have already been taken and avoid duplicated work.
 
 <br /><br />
 
 <img src="./docs/assets/icons/cloud-line.svg" width="12%" align="right"/>
 
 ### Deploy on any Kubernetes cluster
 
-You can deploy BotKube backend on any Kubernetes cluster. It doesn't matter whether it is [K3d](https://k3d.io), managed Kubernetes on a cloud provider, or bare-metal one.
+You can deploy Botkube backend on any Kubernetes cluster. It doesn't matter whether it is [K3d](https://k3d.io), managed Kubernetes on a cloud provider, or bare-metal one.
 
 ## Licence
 

SECURITY.md

@@ -4,7 +4,7 @@
 
 **Please do not report security vulnerabilities through public GitHub issues.**
 
-To report security vulnerabilities in BotKube project, please email [**[email protected]**](mailto:[email protected]) with a detailed description of the issue. If the issue is confirmed, we will release a patch as soon as possible depending on complexity.
+To report security vulnerabilities in Botkube project, please email [**[email protected]**](mailto:[email protected]) with a detailed description of the issue. If the issue is confirmed, we will release a patch as soon as possible depending on complexity.
 
 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 

branding/logos/botkube-black-1000x1000.png

@@ -1,9 +1,9 @@
 FROM alpine:3.15
 ARG botkube_version="dev"
 LABEL org.opencontainers.image.source="[email protected]:kubeshop/botkube.git" \
-      org.opencontainers.image.title="BotKube" \
+      org.opencontainers.image.title="Botkube" \
       org.opencontainers.image.version="${botkube_version}" \
-      org.opencontainers.image.description="BotKube is a messaging bot for monitoring and debugging Kubernetes clusters" \
+      org.opencontainers.image.description="Botkube is a messaging bot for monitoring and debugging Kubernetes clusters" \
       org.opencontainers.image.documentation="https://botkube.io" \
       org.opencontainers.image.licenses="MIT"
 

branding/logos/botkube-black-192x192.png

@@ -12,8 +12,8 @@ COPY $TEST_NAME /test
 LABEL name="botkube" \
       test=$TEST_NAME \
       org.opencontainers.image.source="[email protected]:kubeshop/botkube.git" \
-      org.opencontainers.image.title="BotKube E2 tests" \
-      org.opencontainers.image.description="BotKube E2E tests which are run against BotKube installed on Kubernetes cluster and Slack API." \
+      org.opencontainers.image.title="Botkube E2 tests" \
+      org.opencontainers.image.description="Botkube E2E tests which are run against Botkube installed on Kubernetes cluster and Slack API." \
       org.opencontainers.image.documentation="https://botkube.io" \
       org.opencontainers.image.licenses="MIT"
 

branding/logos/botkube-black-32x32.png

@@ -273,7 +273,7 @@ func run() error {
 			}
 
 			// non-blocking error, move forward
-			logger.Warn("Config Watcher is still not synchronized. Read the logs of the sidecar container to see the cause. Continuing running BotKube...")
+			logger.Warn("Config Watcher is still not synchronized. Read the logs of the sidecar container to see the cause. Continuing running Botkube...")
 		}
 	}
 

branding/logos/botkube-color-1000x1000.png

@@ -10,7 +10,7 @@ communications:
         'alias':
           name: 'SLACK_CHANNEL'
           notification:
-            # -- If true, the notifications are not sent to the channel. They can be enabled with `@BotKube` command anytime.
+            # -- If true, the notifications are not sent to the channel. They can be enabled with `@Botkube` command anytime.
             disabled: false
           bindings:
             executors:
@@ -41,14 +41,14 @@ communications:
     mattermost:
       enabled: false
       url: 'MATTERMOST_SERVER_URL'              # URL where Mattermost is running. e.g https://example.com:9243
-      token: 'MATTERMOST_TOKEN'                 # Personal Access token generated by BotKube user
-      team: 'MATTERMOST_TEAM'                   # Mattermost Team to configure with BotKube
-      botName: 'BotKube'                        # Bot name
+      token: 'MATTERMOST_TOKEN'                 # Personal Access token generated by Botkube user
+      team: 'MATTERMOST_TEAM'                   # Mattermost Team to configure with Botkube
+      botName: 'Botkube'                        # Bot name
       channels:
         'alias':
-          name: 'MATTERMOST_CHANNEL'            # Mattermost Channel for receiving BotKube alerts:
+          name: 'MATTERMOST_CHANNEL'            # Mattermost Channel for receiving Botkube alerts:
           notification:
-            # -- If true, the notifications are not sent to the channel. They can be enabled with `@BotKube` command anytime.
+            # -- If true, the notifications are not sent to the channel. They can be enabled with `@Botkube` command anytime.
             disabled: false
           bindings:
             executors:
@@ -63,21 +63,21 @@ communications:
       enabled: false
       appID: 'APPLICATION_ID'
       appPassword: 'APPLICATION_PASSWORD'
-      botName: 'BotKube'
+      botName: 'Botkube'
       notification:
         type: short
       port: 3978
 
     # Settings for Discord
     discord:
       enabled: false
-      token: 'DISCORD_TOKEN'                    # BotKube Bot Token
-      botID: 'DISCORD_BOT_ID'                   # BotKube Application Client ID
+      token: 'DISCORD_TOKEN'                    # Botkube Bot Token
+      botID: 'DISCORD_BOT_ID'                   # Botkube Application Client ID
       channels:
         'alias':
-          id: 'DISCORD_CHANNEL_ID'            # Discord Channel id for receiving BotKube alerts:
+          id: 'DISCORD_CHANNEL_ID'            # Discord Channel id for receiving Botkube alerts:
           notification:
-            # -- If true, the notifications are not sent to the channel. They can be enabled with `@BotKube` command anytime.
+            # -- If true, the notifications are not sent to the channel. They can be enabled with `@Botkube` command anytime.
             disabled: false
           bindings:
             executors: