Closed mts-dyt closed 1 year ago
Hey @mts-dyt, have you tried to specify which container you want the logs from?
$ kubectl logs -h
...
-c, --container='':
Print the logs of this container
Example:
kubectl logs -n kube-system -c lb-tcp-80 svclb-traefik-e82aa45a-qq7hp on test-cluster
+ trap exit TERM INT
+ echo 10.43.211.164
+ grep -Eq :
+ cat /proc/sys/net/ipv4/ip_forward
+ '[' 1 '!=' 1 ]
+ iptables -t nat -I PREROUTING '!' -s 10.43.211.164/32 -p TCP --dport 80 -j DNAT --to 10.43.211.164:80
+ iptables -t nat -I POSTROUTING -d 10.43.211.164/32 -p TCP -j MASQUERADE
+ '[' '!' -e /pause ]
+ mkfifo /pause
Hey @mts-dyt, I'm closing this issue as resolved. Feel free to reopen the issue if your problem is not resolved 🙂 Ensure you use the latest Botkube version. Cheers!
hi @pkosiec Yes the command is OK but the idea was to able to select the container from slack
Hey @mts-dyt, Ah, you mean the interactive dropdown? If so, we have such issue already: https://github.com/kubeshop/botkube/issues/949. Please follow it for updates. For now this is not planned to any of the upcoming milestones, but that might change soon. Please add a reaction under #949 so that we can see the popularity of the feature request. Thanks!
Overview
Select the container when executing
kubectl logs <pod>
Acceptance Criteria
Reason
When we have multiple containers in a pod, it is always displayed the logs of the first container