Hi All, I am currently working on $subject. Initial idea is to deliver a fully automated, stable Kubernetes deployment experience for the end users of both WSO2 EI and APIM products such that during the process, we can understand how we can improve Kubernetes-common, the base Kubernetes deployment enabling layer as its platform.
Earlier with our old product strategy, we did maintain a repository called, kubernetes-artifacts <https://github.com/wso2/kubernetes-artifacts> where all the product specific artifacts were also kept. Now, we have split this out in to two levels, namely [1] kubernetes-common <https://github.com/wso2/kubernetes-common> - base Kubernetes deployment enabling layer [2] kubernetes-<product-label>, i.e. for example, kubernetes-ei - Product specific kubernetes artifacts that integrates with kubernetes-common However, with our new product strategy and architectural changes, most of the product-specific kubernetes artifacts are not yet done and WSO2 EI, WSO2 APIM are two such products. While there is an on-going effort by Isuru (Isuruh) on finalizing kubernetes-apim related deployment artifacts, I will be working on kubernetes-ei related artifacts as an effort to improve Kubernetes Deployment Support for WSO2 Products. As mentioned above, during this process, we will be also accessing ways of improving Kubernetes-common layer for a much-developer friendly framework in building more customer centric production ready kubernetes deployment artifacts with very minimum effort. Thanks, Dilan. *Dilan U. Ariyaratne* Senior Software Engineer WSO2 Inc. <http://wso2.com/> Mobile: +94766405580 <%2B94766405580> lean . enterprise . middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
