Steady! How thousands of micro services can quickly access Zadig (helm chart)

summary

Helm  As an excellent in the cloud native field  Kubernetes  Applied package management tools , Widely used . However, when the environment increases , Need to be tailored to different environments （ development environment 、 Test environment 、 Pre release environment ...） Customize different  Helm Chart  To configure , Traditional script management is very error prone ; And when the life cycle of the temporary test environment ends , Corresponding  Helm Chart  Configuration loses value , Low input and output .

Zadig  Provides three types of efficient management  Helm Chart  Configured pose ：

• Batch synchronize configuration from code base
  ： take  Helm Chart  The configuration is organized in the code base , Synchronize configuration from the code base , Realize the batch creation of services .

• Use  Helm Chart  Template creation service
  ： abstract  Helm Chart  The configuration template , stay  values  Variables are supported in the file , You can quickly create a service by specifying a few variables , And a set of templates can be reused in multiple environments .

• Use  Helm Chart  Template batch creation service
  ： abstract  Helm Chart  The configuration template , Specify... When creating the service  values  File overwrite template , You can create services in batch , And a set of templates can be reused in multiple environments .

The usage of these scenarios will be described in detail below .

Batch synchronize configuration from code base

apply ： Use  Helm Chart  Manage multiple  K8s YAML  Service configuration , Each service has a separate  YAML  To configure .

Integrate multiple services  YAML  Configure the organization in a  Helm Chart  in , Use  Zadig  Bulk import , Let's say  

voting-demo

  Project as an example ：

• Source code ：
  zadig/voting-app

• service ： Include  5  Micro services （
  db
  /
  redis
  /
  result
  /
  vote
  /
  worker
  ）

• Helm Chart  To configure ： Located under the source code  
  chart
    Catalog , The directory structure is shown below .
  values.yaml
    Including the image information of all services ,
  templates
    The directory contains the configuration of all services , And reference  
  {{ .Values.services. service name .image }}
    As container image information

zadig/examples/voting-app/chart
├── Chart.yaml
├── templates
│ ├── db.yaml
│ ├── redis.yaml
│ ├── result.yaml
│ ├── vote.yaml
│ └── worker.yaml
└── values.yaml

Synchronize from the code base

Enter the service module of the project  ->  Click on

Synchronize from the code base

 ->  Select the code base and  Helm Chart  Directory of files , Click on

load

（ In this case  Zadig  Library  

examples/voting-app/chart

  Catalog ）.

After synchronization , The system will automatically analyze  values.yaml, Resolve multiple service components .

Adding services to the environment

Click on

Join the environment

 ->  Selection environment , Quickly add multiple services to the existing environment with one click .

Use  Helm Chart  Template creation service

apply ： Use  Helm Chart  management  K8s YAML  Service configuration , The configuration structure of each service is isomorphic , The values of different service configurations vary slightly （ such as ： The image names of different services are different 、 Different ports 、 what is needed  CPU/Memory  Different resource restrictions ...）. Abstract the configuration to include variables  Helm Chart  Templates , When creating a service, you only need to configure a few variables .

Let's say  

multi-service-demo

 

Case study

Practice , Some directory structures related to practice are described as follows ： There are three services  

service1

/

service2

/

service3

, By configuring the complete service （ 

k8s-yaml

  Catalog ） Analyze , Abstract out the general  Helm Chart  Service template （

general-chart

  Catalog ）.

zadig/examples/multi-service-demo/
├── general-chart # Helm Chart  Service template
│ ├── Chart.yaml
│ ├── templates
│ │ ├── _helpers.tpl
│ │ ├── deployment.yaml
│ │ └── service.yaml
│ └── values.yaml
├── k8s-yaml #  All services are complete  K8s YAML  To configure
│ ├── service1
│ │ ├── deployment.yaml
│ │ └── service.yaml
│ ├── service2
│ │ ├── deployment.yaml
│ │ └── service.yaml
│ ├── service3
│ │ ├── deployment.yaml
│ │ └── service.yaml

You can see the  

values.yaml

  Custom variables are used in the file  

port

  And system built-in variables  

T-Service

, After creating a service using a template , The variables here will be replaced by rendering .

fullnameOverride: $T-Service$
replicaCount: 1
port: {{.port}}

imagePullSecretsName: "default-registry-secret"

image:
 repository: "ccr.ccs.tencentyun.com/koderover-public/$T-Service$"
 tag: "latest"

resources:
 requests:
 cpu: 10m
 mem: 10Mi

 limits:
 cpu: 20m
 mem: 20Mi

establish  Helm Chart  Templates

Click... In the upper right corner of the project preview page  

Template library

 -> 

Helm Chart

  Get into  Helm Chart  Template management page .

Click on  

+

  New template  ->  Fill in the template name  

multi-service-demo-template

 ->  Select the code base and directory where the template is located  ->  Click on

load

Save template .

In this case  Zadig  Library  

examples/multi-service-demo/general-chart

  Catalog

After importing the template successfully, the effect is as follows , Click the specific file in the template to view its contents , You can assign default values to user-defined variables in the template .

Create a new service using a template

Enter the service module of the project  ->  Click on

Use the template to create a new

 ->  Fill in the service name and select the template , According to the actual configuration of the service , Assign values to variables in the template  ->  Click on

Import

.

After successful import, the effect is as follows , After selecting a service, you can view it in  Zadig  In the platform  values  Preview the content .

The same steps to quickly create a service  

service2

、

service3

.

In this case  

service2

、

service3

The ports of are respectively  20222、20223.

Add services to the environment

Enter the project environment  ->  Click on

Add service

 ->  Select the new service to add the service to the existing environment .

Use  Helm Chart  Template batch creation service

apply ： The existing service configuration uses a separate  Helm Chart  To manage （ One by one access will lead to inefficiency ）. At this point, the service configuration is abstracted as  Helm Chart  Templates , When creating services, use the... Of each service  values  To override the configuration in the template , Services can be accessed in batches  Zadig.

The same to  

multi-service-demo

 

Case study

Practice , Some directory structures related to practice are described as follows ： There are three services  

service1

/

service2

/

service3

, Through a complete  Helm Chart  To configure （ 

full-charts

  Catalog ） Analyze , Abstract out  Helm Chart  Templates （

base-chart

  Catalog ）, And corresponding to each service  values（

values

  Catalog ）.

zadig/examples/multi-service-demo/
├── base-chart # Helm Chart  Service template
│ ├── Chart.yaml
│ ├── templates
│ │ ├── _helpers.tpl
│ │ ├── deployment.yaml
│ │ └── service.yaml
│ └── values.yaml
├── full-charts #  All services are complete 、 independent  Helm Chart  To configure
│ ├── service1
│ │ ├── Chart.yaml
│ │ ├── templates
│ │ └── values.yaml
│ ├── service2
│ │ ├── Chart.yaml
│ │ ├── templates
│ │ └── values.yaml
│ └── service3
│ ├── Chart.yaml
│ ├── templates
│ └── values.yaml
└── values #  Corresponding to each service  values
 ├── service1.yaml
 ├── service2.yaml
 └── service3.yaml


establish  Helm Chart  Templates

There are similar operations in the previous article , No more details here .

The template name created in this example is  

multi-service-demo-base-template

, originate  Zadig  Library  

examples/multi-service-demo/base-chart

  Catalog .

Create a service in batch by using a template

Enter the service module of the project  ->  Click on

Use the template to create a new

 ->  Click on

Batch creation

->  Select a template as well as multiple services  values  File path , Click on

Import

.

In this case  Zadig  Library  

examples/multi-service-demo/values

  Catalog

After successful import, the effect is as follows , After selecting a service, you can view it in  Zadig  In the platform  values  Preview the content .

Add services to the environment

Enter the project environment  ->  Click on

Add service

 ->  Select a new service to batch add the service to the existing environment .

The above three methods successfully connect the service to  Zadig, Then you can use  Zadig  Strong environmental governance and workflow capabilities to build and deploy services 、 Test verification 、 Continuous delivery, etc , Recommended reading ：

• Use  Zadig  workflow

• Zadig  Environmental Science  - K8s Helm Chart  project

• Zadig  version management  - K8s Helm Chart  project

Conclusion

Synchronize from the code base  Helm Chart  Configuration can be done quickly in  Zadig  Create service in medium batch and pull up the environment , Quickly validate the business ; The template function unifies the management of service configuration , Reduce  Helm Chart  The burden of maintenance , Let engineers from the tedious configuration management “ Dirty work is tiring ” Free up , Enter the fast lane of cloud native continuous delivery , More time to create business value .

Zadig, Let engineers focus more on creating ！ Welcome to join  

Make complaints about open source Tucao group

Zadig on Github

 

https://github.com/koderover/zadig

Zadig on Gitee

 

https://gitee.com/koderover/zadig