Nice. I tried playing with it but I have multiple file types in my repo, not just Kubernetes. Can I still run those in Datree or will it fail?
Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
11–20 of 44 posts
Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#12Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#13K8s can really be a pain especially for larger teams. This is a breath of fresh air!
Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#14Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#15Wish this tool was in existence two years ago, would have saved me many 3am wakeup calls.
Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#16Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#17Tools nowadays are so cumbersome it’s so easy to misconfigure them.
Thanks for sharing
Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#18Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#19Why is this whole thread dead? Just because of the blatant appearance of astroturf or what?
Sometimes it happens inadvertently (e.g. users find out about the thread and rush in to 'help'), but obviously we want the discussion here to be substantive.
Re: Show HN: Datree (YC W20): Prevent K8s misconfigurations from reaching production
#20Why is this whole thread dead? Just because of the blatant appearance of astroturf or what?
I killed all the booster comments. We tell YC startups not to do that. All startups, of course, but especially YC startups. Sometimes it happens inadvertently (e.g. users find out about the thread and rush in to 'help'), but obviously we want the discussion here to be substantive.
I look forward to hearing your feedback! Thank you