Possible Issues with install/migrate for the botkube cloud setup

[Nalum]

Description

Attempted to setup a botkube instance on a local kind cluster. Using botkube migrate and botkube install I hit issues around merging the app configuration.

Expected behavior

Expected the botkube instance to successfully connect and report into the botkube cloud dashboard.

Actual behavior

The migrate command reported an issue with the CLI and Agent version not matching the version constraints:

❯ botkube migrate
Migrating Botkube installation to Cloud
 ? The migration job already exist. Do you want to re-create it? Yes
 ✓ Fetching configuration [took 8s]
 • Checking if Botkube version "v1.6.0" can be migrated safely
?
The migration process for the Botkube CLI you're using (version: "1.6.0") wasn't tested with your Botkube version on your cluster ("1.6.0").
Botkube version constraints for the currently installed CLI: >= 1.0, < 1.3
We recommend upgrading your CLI to the latest version. In order to do so, navigate to https://docs.botkube.io/.

Do you wish to continue? (y/N)

Continuing the migrate resulted in the same error as the install command below:

❯ botkube install --version=v1.6.0 \
  --set config.provider.endpoint=https://api.botkube.io/graphql \
  --set config.provider.identifier=5f...ad \
  --set config.provider.apiKey=key:ac...1a
Installing Botkube on cluster...
 • Installation details:

      Version               v1.6.0
      Helm repository       https://charts.botkube.io/
      Kubernetes Context    kind-nalum-oci

 ✓ Creating namespace botkube [took 0s]
 ✓ Loading botkube Helm chart [took 0s]
 ✓ Scheduling botkube Helm chart [took 0s]
 ✓ Waiting until Botkube Pod is running [took 5s]
 • Streaming logs...
    Pod: botkube-5bb48bc47-bw6fj
     FATA while running application: while merging app configuration: found critical validation errors: 3 errors occurred:
        * Key: 'Config.Actions[show-logs-on-error].Bindings.k8s-default-tools_jJkwz' 'k8s-default-tools_jJkwz' binding not defined in Config.Executors
        * Key: 'Config.Actions[describe-created-resource].Bindings.k8s-default-tools_jJkwz' 'k8s-default-tools_jJkwz' binding not defined in Config.Executors
        * Key: 'Config.Communications' Communications must contain at least 1 item
 • Finished logs streaming

  │ Botkube v1.6.0 installation failed 😿
  │ To get all Botkube logs, run:
  │
  │   kubectl logs -n botkube pod/botkube-5bb48bc47-bw6fj

  │ To resolve the issue, see Botkube documentation on https://docs.botkube.io/operation/common-problems.
  | If that doesn't help, join our Slack community at https://join.botkube.io.
  │ We'll be glad to get your Botkube up and running!

Error: pod restarted with non zero exit code

Steps to reproduce

Run botkube migrate to be able to see the constraint message.

I attempted to reproduce the configuration merge issue the following day but was not able to, it may have been a transient issue. Just reporting it here to have it recorded.

[pkosiec]

Hi @Nalum, thank you for reporting the issue. We'll try to reproduce it (and fix it, if necessary) soon 👍 Cheers!

---

AC

• Fix constraint
• Try to reproduce the issue:
  • Test it with enabled and disabled actions
• Double check the telemetry for the command