Adyanth Hosavalike
Adyanth Hosavalike
Yeah! That is a good solution to implement.
I agree. Issue could be up for tracking in the future, or if you don't think it is feasible to be implemented in frp, feel free to close!
> move separate controllers into their own packages Interesting, the access tunnel can surely be moved, but the rest of them are bound together because they share functionality. I am...
It can be run in k8s right now, just that it needs a PVC and an external DB (sqlite is not recommended on networked file systems, unless using a block...
The way it is structured right now, the alerting intervals are handled through context, which needs an active alert object to test on, which is not done in `test_routing.go`. Please...
Interesting, yeah there is a way to mark resources as preventing deletion of its parent with ownerRefs (if what I understood was correct from https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/). That would solve this problem...
Okay, I have an idea for this. Instead of each tunnel binding triggering the config map (which looks at all other tunnel bindings to recreate the ConfigMap), we can have...
Trying that solution in #140
Drawing inspiration from role/rolebindings, they just work, but that could be due to the fact that they are checked when needed, unlike our tunnel binding. I'm a little hesitant in...
`Owns` does not work because we would end up with multiple owners (Each tunnel binding trying to own the tunnel). Watches is what I tried initially, but saw two issues...