Tim Malone

Related: > We’ve not yet done any research to see if S3’s new guarantees are sufficient for that model to be safe, and I also want to be transparent that...

It'd be good to update https://github.com/bitnami-labs/kubewatch/blob/master/kubewatch-service-account.yaml with the above too 😃

Ran into this issue as well. It might be a good idea to update https://github.com/bitnami-labs/kubewatch/blob/master/kubewatch.yaml :) (and if it's old, remove it - or at least not link to it...

This issue is similar to #135

Here's an updated `kubewatch.yaml` for others coming across this: ```yaml apiVersion: v1 kind: Pod metadata: name: kubewatch namespace: default spec: serviceAccountName: kubewatch containers: - image: bitnami/kubewatch imagePullPolicy: Always name: kubewatch...

I experienced the same issue and got quite confused - tried turning off SSL support, still got the error, scratched my head for awhile... and then Googling lead me here....

I think you (aka bot user, whoever owns the token) might have to actually be in the channel to set its topic.

> How about AWS::Route53::RecordSet resoures? @gietschess IIRC these might actually just work by re-creating them over the top of existing resources, i.e. effectively 'adopting' existing resources into management without needing...

Thanks for the heads up @danmichaelo. Vitaliy is still active on Twitter so I have [tweeted him](https://twitter.com/tdmalone/status/909008309809590272) with a link to this issue.