Taylor Price

I am also hitting this issue. I see this on sensors and event sources. Rescheduling onto a 'fresh' box does seem to help for a while, but it does eventually...

> In `EventSource` and `Sensor` spec, there's a way to configure pod `SecurityContext`: > > > > ```yaml > > spec: > > template: > > securityContext: > > sysctls:...

I think most people would expect it to work like cron, where jobs would overlap if they take too long to run.

True, it probably is safer all around not to allow a job to overlap. Both because of the way background workers are and also because of the way sql works...

I would also mention that the docs aren't super clear on how this integration is supposed to work - I couldn't get schemahero to authenticate to vault, and I couldn't...

Being able to create facets via terraform would be really great. Is there an ETA on this?

I've also seen this issue, although for me it's started happening even when the protection level doesn't match - I want to set push to 'maintainers' and merge to 'developers'....

When you talk about a workaround that DOESN'T involve recreating the statefulset, what do you mean? I think the only real option for this is to manually edit the existing...

> We run Timescale on EKS. Here are the steps that we follow. > > 1. Modify the EBS volumes. > 2. Update the PVC > 3. Delete the statefulset...

@Nainterceptor since k8s 1.15 (technically before, but that's when it was enabled by default) you can resize an in-use pvc, provided your underlying driver supports it: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim As far as...