Hi erdengk, > so I > am ready to apply for this GSoC idea to improve integration test and > deployment methods.[1]
Welcome! Have a good time~ > I have implemented a Helm repository > <https://github.com/erdengk/shenyu-helm-chart> [2] which can currently > deploy Shenyu-admin and Shenyu-bootstrap through the Helm. > I also uploaded the deployment file to Helm's official repository through > my Google account. Click this link > <https://artifacthub.io/packages/helm/shenyu-test/shenyu> to access.[3] I think this is a great job :) > There are a few questions I would like to ask the community for advice. 1. IMO, we'd better be able to publish on artifacthub.io 2. ShenYu doesn't have an artifacthub account yet, and I'm not sure if Apache has an official account (it doesn't seem to have one). I think it is possible to create a new account, but I am not sure whether this is in compliance with the ASF regulations and need to wait for the confirmation of the folks. 3. If we need github pages, I see that we already have github pages in the main repository, so we'd better create a new repository to avoid conflicts with git pages in the main repository. 4. Does it mean that we have to release multiple times and release all historical versions? I think we only need to start the release from the current version (2.4.3), because users who use the previous version have already deployed it normally, WDYT? Kevin <[email protected]> 于2022年3月21日周一 03:13写道： > > Dear Community Developer > > I am a student who loves open source, and the GitHub id is erdengk. In > February of this year, I saw an about the shenyu community in the GSoC-CN > group and became interested in the community. My own learning direction is > distributed and cloud-native. The importance of gateways as the entrance of > distributed applications is self-evident, so I am very interested in shenyu > gateways. With the help of the community, I successfully resolved some > issues. With the merging of my pr, I have also built up my confidence, so I > am ready to apply for this GSoC idea to improve integration test and > deployment methods.[1] > > While learning about the idea, I ran into a few questions and needed to ask > the community for input. > > Part of this idea is to deploy shenyu using Helm, Helm is a package > management tool for Kubernetes. Using Helm, we can deploy resources > required by Kubernetes with one click, and we can also implement version > upgrades, rollbacks, and other operations. It is similar to what Maven does > in Java. > > I have implemented a Helm repository > <https://github.com/erdengk/shenyu-helm-chart> [2] which can currently > deploy Shenyu-admin and Shenyu-bootstrap through the Helm. > I also uploaded the deployment file to Helm's official repository through > my Google account. Click this link > <https://artifacthub.io/packages/helm/shenyu-test/shenyu> to access.[3] > > There are a few questions I would like to ask the community for advice. > > 1. Do we need to publish Shenyu's deployment documentation on Helm's > official repository artifacthub.io? > 2. If we want to publish on artifacthub <https://artifacthub.io/>, we need > to create an account to publish Helm documents. Does the community have an > account on this site? Do we need an official Apache account to do this? > 3. If we want to publish to Helm's official repository, artifacthub > <https://artifacthub.io/> needs to scan for updates using GitHub Pages. Are > we doing this in the shenyu repository, or do we create a new repository? > 4. Regarding the deployment versions provided by Helm, my suggestion is to > provide stable deployment packages for each version and the latest > deployment packages for each version. how about this? > > > [1]: https://github.com/apache/incubator-shenyu/issues/2890 > [2]: https://github.com/erdengk/shenyu-helm-chart > [3]: https://artifacthub.io/packages/helm/shenyu-test/shenyu
