Plans for Installation and Deployment Optimization

[zhu733756]

Hey guys, we have plans for installation and deployment optimization for KubeEdge, the installation tool keadm will be refactored.

If you have features to achieve or to get involved in the development, please see the project form below, and you can add other todos here as you want:

• [x] 1. Cloud side: Use tools like istioctl to integrate cloud components and provide stronger functions including the existing helm installation, and the newer keadm will only install containerized Cloudcore.
• [x] 2. Edge side: Provides a container service that can run and manage static resources and binaries.
• [ ] 3. Edge side: Provides rpm domestic/international source integration, to download managed static files and binary files.
• [x] 4. Cloud side: As a supplement, we will provide documents for installing CloudCore in process mode.
• [ ] 5. CI & CD: Mirror warehouse synchronization, regular mirror building, automatic release, and other auxiliary functions development and construction with Github actions.

/cc @fisherxu @zc2638 @gy95 @zhu733756

[gy95]

some work about cloudcore container deployment: maybe we can define required k8s resources in a string, or just use go embed https://github.com/kubeedge/kubeedge/pull/2853

[zc2638]

some work about cloudcore container deployment: maybe we can define required k8s resources in a string, or just use go embed #2853

Because we need to support helm deployment, there should not be two yaml definitions, so a better way is to generate yaml resources through helm

[gy95]

some work about cloudcore container deployment: maybe we can define required k8s resources in a string, or just use go embed #2853

Because we need to support helm deployment, there should not be two yaml definitions, so a better way is to generate yaml resources through helm

you mean the new keadm will only support install cloudcore using helm? : https://github.com/kubeedge/kubeedge/blob/master/build/helm/cloudcore/README.md#install-examples or maybe also need to support common pod deployment?

[zhu733756]

some work about cloudcore container deployment: maybe we can define required k8s resources in a string, or just use go embed #2853

Because we need to support helm deployment, there should not be two yaml definitions, so a better way is to generate yaml resources through helm

you mean the new keadm will only support install cloudcore using helm? : https://github.com/kubeedge/kubeedge/blob/master/build/helm/cloudcore/README.md#install-examples or maybe also need to support common pod deployment?

Yeah, keadm will support the function of what helm can do. I think the common deployment can be included in this case. Through customization, we could achieve flexible installation of all containerized deployments. In addition, as a supplement, we will provide documents for installing CloudCore in process mode.

[zc2638]

you mean the new keadm will only support install cloudcore using helm? : https://github.com/kubeedge/kubeedge/blob/master/build/helm/cloudcore/README.md#install-examples or maybe also need to support common pod deployment?

Sure, as @zhu733756 say. Two deployment methods will be supported by default, one is helm and the other is native k8s resource deployment. k8s resources are dynamically generated through helm.

[gy95]

I would like to join this task, what work could I participate in? :) not sure how to implement this keadm optimization 😆

[zhu733756]

I would like to join this task, what work could I participate in? :) not sure how to implement this keadm optimization 😆

Let's talk about it tomorrow on the zoom. @gy95

[stale[bot]]

Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).