Hi Folks,
After several months of offline and F2F discussions, we want to inform the community that we are forming a Kubernetes Policy WG with initial members from Huawei, Styra, RedHat, Google and China Mobile. 1. Motivation Policy is an important feature and we have seen policy support scattered across multiple modules in Kubernetes, for example policy related components could be found in identity services, networking services, storage services, multi-cluster federation, RBAC and many other areas, with different degree of maturity and also different motivations for specific problems. The purpose of establishing a Policy WG within Kubernetes community is try to provide an overall architecture that describes both the current policy related implementations as well as future policy related proposals in Kubernetes. Through a collaborative method, we want to present both dev and end user a universal view of policy architecture in kubernetes. It should be noted that it is not the job of this WG to redefine and replace any of the existing implementations which are the results of community discussion and consensus. This WG is more about looking forward whereas provide a summarized review of the current implementation, both of which will be fit into a bigger picture. It is possible that if this WG were to be proved successful we might consider to expanding it to a more broader CNCF context (with for example Istio/envoy's policy arch in mind). However at the moment we will concentrate on Kubernetes community. 2. Rationale for a WG instead of SIG Policy is a cross-SIG topic hence we feel that a WG is better fit for our purpose and goals. Related SIGs includes but not limited to: sig-architecture, sig-auth, sig-network, sig-node, sig-on-premise, sig-multicluster, sig-scheduling, sig-storage, wg-multitenancy, wg-resource-management. WG structure is also better for cross-community communication since there are other open source communities such as OPNFV, OpenStack, OpenSDS, OpenDaylight might have interested in Kubernetes policy work. We could establish WG level discussions among various communities. 3. MVP goals before CloudNativeCon EU 2018 a. Complete the Policy WG Design Document <https://docs.google.com/document/d/1Ht8wpj4j9YfAA7aVv9Yn3Ci1T_MLMWt0DBr0QmxI2OM/edit?usp=sharing> b. Complete all the procedure requirement for the establishment of the WG c. Establish a good communication mechanism with related SIGs/WGs d. Arrange a first Policy WG session at CloudNativeCon EU. 4. Call for participation and immediate next step A successful and healthy WG could not be done without a great community participation, therefore we are looking for any devs/users that is interested in policy topic to participate in the WG discussion. We have created a google group <https://groups.google.com/forum/#!forum/kubernetes-wg-policy> where such discussions could happen. People could also directly reach out to the lead contacts from the five founding companies listed in the design document for any questions they shall have. Our immediate next step will be to setup an official bi-weekly or weekly conf call starting the discussion for the design document on the kubernetes policy architecture overview and requirements and so forth. Please feel free to join the conversation and look forward to a great year for policy development in Kubernetes :) -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
