It is difficult for k8s beginners to add services about zadig

[landylee007]

zadig v1.6.0 is now released which included helm chart/k8s yaml templates modules. Operations engineers only need to configure the template once, and developer can quickly define the service very simple such as service name/ variables. @hoozecn @nighca

[hoozecn]

A graphical guidance would be great like kubesphere did.

https://kubesphere.io/docs/project-user-guide/application-workloads/services/#create-a-stateless-service

[lilianzhu]

First of all, If k8s beginners use gui to configure services, they still need understand the meaning of the fields, which will be more black box; secondly, the same team usually does not have many different service templates in the same business scenario, we consider that it may be possible to improve.

1. support that save the existing service yml to become a yml template, convenient to refer to the next use
2. zadig IDE provides more convenient yml validation capabilities, let's support developers in the cloud native way.
3. zadig support some general templates such as stateless service、stateful service、some middleware .etc.
   btw, do u have any interested in this improvement? @hoozecn

[lilianzhu]

What do you think of the above ideas? @nighca

[nighca]

IMO template may not be so helpful. It requires k8s knowledge to edit on templates. Since different parts of k8s config are related, it is easy to make mistakes.

zadig IDE provides more convenient yml validation capabilities, let's support developers in the cloud native way.

I will vote for this.

More specifically, I think a tool (GUI) to help generate k8s config will be great. This tool collects info about application/service from users and translates it to k8s config.

[hoozecn]

IMO template may not be so helpful. It requires k8s knowledge to edit on templates. Since different parts of k8s config are related, it is easy to make mistakes.

I agree. Templated YAML is still complex for beginners and it's easy to make mistakes.

The gui default layout could be very simple:

• A service name
• An image name

That's it and the two arguments are enough for the following building config.

If people have an advanced knowledge of k8s, he/she can use an advanced configuration GUI or the yaml editor.