You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When BotKube is deployed in multiple cluster with settings.allowkubectl:false set in the config, it returns redundant error messages when BotKube commands are executed.
Sample messages (provided by an user on BotKube slack)
Sorry, the admin hasn't given me the permission to execute kubectl command on cluster 'cluster-0hyv0'.
Sorry, the admin hasn't given me the permission to execute kubectl command on cluster 'cluster-0253f'.
Sorry, the admin hasn't given me the permission to execute kubectl command on cluster 'cluster-6toxk'.
Sorry, the admin hasn't given me the permission to execute kubectl command on cluster 'cluster-08cka'.
Cluster: cluster-mx8ae
No resources found in default namespace.
To Reproduce
Steps to reproduce the behavior:
Deploy BotKube on multiple clusters with the same token
Execute @BotKube get pods command
Expected behavior
BotKube should get response only from the cluster which is configured for the channel or whose name is passed with --cluster-name flag
The text was updated successfully, but these errors were encountered:
Describe the bug
When BotKube is deployed in multiple cluster with
settings.allowkubectl:false
set in the config, it returns redundant error messages whenBotKube
commands are executed.Sample messages (provided by an user on BotKube slack)
To Reproduce
Steps to reproduce the behavior:
@BotKube get pods
commandExpected behavior
BotKube should get response only from the cluster which is configured for the channel or whose name is passed with
--cluster-name
flagThe text was updated successfully, but these errors were encountered: