Over at VMWare we still do lots of upstream engineering. A few projects I'm currently involved with... A few people have asked about some sample projects ... so I figured I'd write this up in a single place.
Rebuilding the Kube Proxy ~ https://github.com/kubernetes-sigs/kpng/ KPNG is a project that replaces the kube proxy w/ a GRPC based implementation. As a GRPC implementation, KPNG makes it so that you can run the "brain" part of the proxy in one place, and the "backend" in another place. I've done a few demonstrations of this recently. Here's a recent kubecon talk that we gave about how it works, in general https://youtu.be/THaDy6u-Cgk?t=853
The ongoing networkpolicy conformance Initiative: which initially was published here https://kubernetes.io/blog/2021/04/20/defining-networkpolicy-conformance-cni-providers/ . At this point, I think the next step will be moving cyclonus to a kubernetes-sigs/ repository... This gives us the ability to compare network policy implementations from different providers in a single truth table.
https://github.com/kubernetes-sigs/sig-windows-dev-tools/ We created this project about a year ago, it's now the defact environment we use for developing and testing new windows features. The nice thing about it is that it spins up a linux and windows VM directly from source... so you can hack up the kubernetes/, say, kubelet (Aravindh at red hat demo'd how he uses it for node logs), and then test a feature from source on your local laptop. It uses virtualbox but we'd love to add a other providers that vagrant supports (i.e. EC2, VSphere, ...) .
The overall workflow results in a 2 VM setup like this, (usually you'd make winw1 from a specific K8s fork)
The windows operational readiness specification, Heres a recent video where we went over how the dev-tools and windows operational-readiness KEP https://youtu.be/3Z0NOrETjxY?t=2973 work . Our overall KEP merged recently, and the code for this repo now lives here https://github.com/kubernetes-sigs/windows-operational-readiness . This will give us a single windows standard (similar to the conformance standard for linux).
Overall the way were defining the specification is by wrapping underlying ginkgo hooks:
No comments:
Post a Comment