3 ms·
Yeah client-go typed clientsets are codegened. It would be really labor intensive (and error prone) to write go code for every deployment. May I suggest a midd
by dilyevsky 8y ago
Yeah client-go typed clientsets are codegened. It would be really labor intensive (and error prone) to write go code for every deployment.
May I suggest a middle ground =) github.com/stripe/skycfg (checkout //_examples/k8s that I added)
- dqpb 8y agoIt would be less labor intensive and less error prone.
- happythought 8y agoI’m interested in learning that model, but a readme in there that explains how to go from nothing to a deployment might help. Edit: also the fact that you have a 4 month old outstanding pull request isn’t giving me any warm fuzzies about the maintenance and velocity of skycfg.
- dilyevsky 8y agonginx.cfg and app.cfg have an example deployment for nginx and the rest is covered in main README. Yeah not sure what is going on with that pr, tbh i forgot about it b/c we implement it in our own runtime. I got a bunch of others merged quickly since then.
- happythought 8y agoThanks, I saw those and they seem clear enough. So the go code is unrelated to nginx.cfg and app.cfg?
- dilyevsky 8y agoThe go code under _examples/k8s is a demo client that will actually stuff `main` output into Kubernetes api endpoint.