Beni Cherniavsky-Paskin
Beni Cherniavsky-Paskin
Have you seen the readme section about config security? File access (**EDIT: and arbitrary command execution!**) can be disabled (at the cost that configs referencing external certs etc. won't work)....
If your use case takes zero inputs from your server, all data comes from customer, then its _maybe_ ok, as in a customer can only attack themselves. But there's still...
- What about Remove deprecated `KubeException` #293? => Not now. As explained there, `HttpError` is not sufficient, we need some top-level exception. Should probably introduce a `Kubeclient::Error` but that's a...
Apologies for delays. Working from home with kids has been... challenging. I hope to get a lot done next week.
> get rid of most of the api That will be an entirely different gem :smile: There is a non-breaking road though: first implement #332, then much later see how...
- [ ] `.rest_client` is definitely going private (or away) to unblock #466.
`master` is already v5, recent releases were from backports to `v4.y` branch
Paternity leave ended :baby:, sleeplessness continues, I didn't make progress I hoped for :-( - If someone wants to help, one simple but important step is update changelog with everything...
Nice. 2 small concerns: 1. Do we also need JSON merge patch and JSON patch variants? Might be worth it for orthogonality alone; also, CRDs don't support strategic merge. 2....
BTW, are these really adding functionality vs doing patch on the whole object only touching `status` part? I think (untested) that works too. I suspect the API has `foo/status` endpoints...