Helm部署xxl-job-admin到K8S集群

怼烎@ 2023-09-29 07:08 19阅读 0赞

本文介绍部署的环境是基于helm 3.x，aws的eks集群环境

假定已经安装好helm3,kubectl等工具

### 准备xxl-job数据库 ###

以下是基于xxl-job-admin 发布的2.3.0版本为基准进行部署

---------------------------------xxl-job-admin-----------------------------------#
    # XXL-JOB v2.3.0
    # Copyright (c) 2015-present, xuxueli.
    CREATE database if NOT EXISTS `xxl_job` default character set utf8mb4 collate utf8mb4_unicode_ci;
    use `xxl_job`;
    
    SET NAMES utf8mb4;
    CREATE TABLE `xxl_job_info` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `job_group` int(11) NOT NULL COMMENT '执行器主键ID',
      `job_desc` varchar(255) NOT NULL,
      `add_time` datetime DEFAULT NULL,
      `update_time` datetime DEFAULT NULL,
      `author` varchar(64) DEFAULT NULL COMMENT '作者',
      `alarm_email` varchar(255) DEFAULT NULL COMMENT '报警邮件',
      `schedule_type` varchar(50) NOT NULL DEFAULT 'NONE' COMMENT '调度类型',
      `schedule_conf` varchar(128) DEFAULT NULL COMMENT '调度配置，值含义取决于调度类型',
      `misfire_strategy` varchar(50) NOT NULL DEFAULT 'DO_NOTHING' COMMENT '调度过期策略',
      `executor_route_strategy` varchar(50) DEFAULT NULL COMMENT '执行器路由策略',
      `executor_handler` varchar(255) DEFAULT NULL COMMENT '执行器任务handler',
      `executor_param` varchar(512) DEFAULT NULL COMMENT '执行器任务参数',
      `executor_block_strategy` varchar(50) DEFAULT NULL COMMENT '阻塞处理策略',
      `executor_timeout` int(11) NOT NULL DEFAULT '0' COMMENT '任务执行超时时间，单位秒',
      `executor_fail_retry_count` int(11) NOT NULL DEFAULT '0' COMMENT '失败重试次数',
      `glue_type` varchar(50) NOT NULL COMMENT 'GLUE类型',
      `glue_source` mediumtext COMMENT 'GLUE源代码',
      `glue_remark` varchar(128) DEFAULT NULL COMMENT 'GLUE备注',
      `glue_updatetime` datetime DEFAULT NULL COMMENT 'GLUE更新时间',
      `child_jobid` varchar(255) DEFAULT NULL COMMENT '子任务ID，多个逗号分隔',
      `trigger_status` tinyint(4) NOT NULL DEFAULT '0' COMMENT '调度状态：0-停止，1-运行',
      `trigger_last_time` bigint(13) NOT NULL DEFAULT '0' COMMENT '上次调度时间',
      `trigger_next_time` bigint(13) NOT NULL DEFAULT '0' COMMENT '下次调度时间',
      PRIMARY KEY (`id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_log` (
      `id` bigint(20) NOT NULL AUTO_INCREMENT,
      `job_group` int(11) NOT NULL COMMENT '执行器主键ID',
      `job_id` int(11) NOT NULL COMMENT '任务，主键ID',
      `executor_address` varchar(255) DEFAULT NULL COMMENT '执行器地址，本次执行的地址',
      `executor_handler` varchar(255) DEFAULT NULL COMMENT '执行器任务handler',
      `executor_param` varchar(512) DEFAULT NULL COMMENT '执行器任务参数',
      `executor_sharding_param` varchar(20) DEFAULT NULL COMMENT '执行器任务分片参数，格式如 1/2',
      `executor_fail_retry_count` int(11) NOT NULL DEFAULT '0' COMMENT '失败重试次数',
      `trigger_time` datetime DEFAULT NULL COMMENT '调度-时间',
      `trigger_code` int(11) NOT NULL COMMENT '调度-结果',
      `trigger_msg` text COMMENT '调度-日志',
      `handle_time` datetime DEFAULT NULL COMMENT '执行-时间',
      `handle_code` int(11) NOT NULL COMMENT '执行-状态',
      `handle_msg` text COMMENT '执行-日志',
      `alarm_status` tinyint(4) NOT NULL DEFAULT '0' COMMENT '告警状态：0-默认、1-无需告警、2-告警成功、3-告警失败',
      PRIMARY KEY (`id`),
      KEY `I_trigger_time` (`trigger_time`),
      KEY `I_handle_code` (`handle_code`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_log_report` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `trigger_day` datetime DEFAULT NULL COMMENT '调度-时间',
      `running_count` int(11) NOT NULL DEFAULT '0' COMMENT '运行中-日志数量',
      `suc_count` int(11) NOT NULL DEFAULT '0' COMMENT '执行成功-日志数量',
      `fail_count` int(11) NOT NULL DEFAULT '0' COMMENT '执行失败-日志数量',
      `update_time` datetime DEFAULT NULL,
      PRIMARY KEY (`id`),
      UNIQUE KEY `i_trigger_day` (`trigger_day`) USING BTREE
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_logglue` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `job_id` int(11) NOT NULL COMMENT '任务，主键ID',
      `glue_type` varchar(50) DEFAULT NULL COMMENT 'GLUE类型',
      `glue_source` mediumtext COMMENT 'GLUE源代码',
      `glue_remark` varchar(128) NOT NULL COMMENT 'GLUE备注',
      `add_time` datetime DEFAULT NULL,
      `update_time` datetime DEFAULT NULL,
      PRIMARY KEY (`id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_registry` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `registry_group` varchar(50) NOT NULL,
      `registry_key` varchar(255) NOT NULL,
      `registry_value` varchar(255) NOT NULL,
      `update_time` datetime DEFAULT NULL,
      PRIMARY KEY (`id`),
      KEY `i_g_k_v` (`registry_group`,`registry_key`,`registry_value`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_group` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `app_name` varchar(64) NOT NULL COMMENT '执行器AppName',
      `title` varchar(12) NOT NULL COMMENT '执行器名称',
      `address_type` tinyint(4) NOT NULL DEFAULT '0' COMMENT '执行器地址类型：0=自动注册、1=手动录入',
      `address_list` text COMMENT '执行器地址列表，多地址逗号分隔',
      `update_time` datetime DEFAULT NULL,
      PRIMARY KEY (`id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_user` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `username` varchar(50) NOT NULL COMMENT '账号',
      `password` varchar(50) NOT NULL COMMENT '密码',
      `role` tinyint(4) NOT NULL COMMENT '角色：0-普通用户、1-管理员',
      `permission` varchar(255) DEFAULT NULL COMMENT '权限：执行器ID列表，多个逗号分割',
      PRIMARY KEY (`id`),
      UNIQUE KEY `i_username` (`username`) USING BTREE
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    CREATE TABLE `xxl_job_lock` (
      `lock_name` varchar(50) NOT NULL COMMENT '锁名称',
      PRIMARY KEY (`lock_name`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    INSERT INTO `xxl_job_group`(`id`, `app_name`, `title`, `address_type`, `address_list`, `update_time`) VALUES (1, 'xxl-job-executor-sample', '示例执行器', 0, NULL, '2018-11-03 22:21:31' );
    INSERT INTO `xxl_job_info`(`id`, `job_group`, `job_desc`, `add_time`, `update_time`, `author`, `alarm_email`, `schedule_type`, `schedule_conf`, `misfire_strategy`, `executor_route_strategy`, `executor_handler`, `executor_param`, `executor_block_strategy`, `executor_timeout`, `executor_fail_retry_count`, `glue_type`, `glue_source`, `glue_remark`, `glue_updatetime`, `child_jobid`) VALUES (1, 1, '测试任务1', '2018-11-03 22:21:31', '2018-11-03 22:21:31', 'XXL', '', 'CRON', '0 0 0 * * ? *', 'DO_NOTHING', 'FIRST', 'demoJobHandler', '', 'SERIAL_EXECUTION', 0, 0, 'BEAN', '', 'GLUE代码初始化', '2018-11-03 22:21:31', '');
    INSERT INTO `xxl_job_user`(`id`, `username`, `password`, `role`, `permission`) VALUES (1, 'admin', 'e10adc3949ba59abbe56e057f20f883e', 1, NULL);
    INSERT INTO `xxl_job_lock` ( `lock_name`) VALUES ( 'schedule_lock');
    
    commit;

### 定义helm部署k8s相关的文件 ###

以下操作均在同一个目录下，比如/home/data/

#### 定义deployment.yaml文件 ####

$vi deployment.yaml

apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: "{
        { .Values.appName }}-v1"
      labels:
        app: {
        {
         .Values.appName }}
        version: v1
    spec:
      replicas: {
        {
         .Values.replicaCount }}
      selector:
        matchLabels:
          app: {
        {
         .Values.appName }}
          version: v1
      template:
        metadata:
          labels:
            app: {
        {
         .Values.appName }}
            version: v1
        spec:
          serviceAccountName: {
        {
         .Values.serviceAccount.name }}
          containers:
            - name: {
        {
         .Values.appName }}
              image:  "{
        { .Values.image.repository }}:{
        { .Values.image.tag }}"
              imagePullPolicy: {
        {
         .Values.image.pullPolicy }}
              ports:
                - containerPort: {
        {
         .Values.service.port }}
              env:
              #  替换yaml文件中的mysql地址
              - name: PARAMS
                value: "--spring.datasource.url=jdbc:mysql://ip:3306/xxl_job?useUnicode=true&characterEncoding=UTF-8&autoReconnect=true&serverTimezone=Asia/Shanghai --spring.datasource.username=admin --spring.datasource.password=Volvo2021"

其中数据库服务器 改为我们自己实际的服务器地址

#### 定义service.yaml文件 ####

$vi service.yaml

apiVersion: v1
    kind: Service
    metadata:
      name: {
        {
         .Values.appName }}
      labels:
        app: {
        {
         .Values.appName }}
        service: {
        {
         .Values.appName }}
    spec:
      ports:
      - port: {
        {
         .Values.service.port }}
        name: http
      type: NodePort
      selector:
        app: {
        {
         .Values.appName }}
    ...
    ---
    apiVersion: v1
    kind: ServiceAccount
    metadata:
      name: {
        {
         .Values.serviceAccount.name }}
      labels:
        account: {
        {
         .Values.appName }}

#### 定义values.yaml文件 ####

$vi values.yaml

# Default values for istio-demo.
    # This is a YAML-formatted file.
    # Declare variables to be passed into your templates.
    replicaCount: 1
    image:
      repository: docker.io/xuxueli/xxl-job-admin
      pullPolicy: Always
      # Overrides the image tag whose default is the chart appVersion.
      tag: "2.3.0"
    
    imagePullSecrets: []
    
    appName: "xxl-job-admin"
    fullnameOverride: "xxl-job-admin"
    
    serviceAccount:
      # Specifies whether a service account should be created
      create: true
      # Annotations to add to the service account
      annotations: {
        }
      # The name of the service account to use.
      # If not set and create is true, a name is generated using the fullname template
      name: "svcat-xxl-job-admin"
    
    
    
    podAnnotations: {
        }
    
    podSecurityContext: {
        }
    # fsGroup: 2000
    
    securityContext: {
        }
      # capabilities:
      #   drop:
      #   - ALL
      # readOnlyRootFilesystem: true
      # runAsNonRoot: true
    # runAsUser: 1000
    
    service:
      type: ClusterIP
      port: 8080
      
    resources: {
        }
      # We usually recommend not to specify default resources and to leave this as a conscious
      # choice for the user. This also increases chances charts run on environments with little
      # resources, such as Minikube. If you do want to specify resources, uncomment the following
      # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
      # limits:
      #   cpu: 100m
      #   memory: 128Mi
      # requests:
      #   cpu: 100m
    #   memory: 128Mi
    
    autoscaling:
      enabled: false
      minReplicas: 1
      maxReplicas: 100
      targetCPUUtilizationPercentage: 80
      targetMemoryUtilizationPercentage: 80
    
    nodeSelector: {
        }
    
    tolerations: []
    
    affinity: {
        }

### 创建chart ###

$helm create xxl-job-admin

### 更新chart ###

$rm -rf xxl-job-admin/templates/\*  
$rm -rf xxl-job-admin/values.yaml  
$cp -r /home/data/deployment.yaml xxl-job-admin/templates/deployment.yaml  
$cp -r /home/data/service.yaml xxl-job-admin/templates/service.yaml  
$cp -r /home/data/values.yaml xxl-job-admin/values.yaml

### chart打包 ###

$helm package xxl-job-admin --version=1.0

### 安装部署到k8s ###

$helm install xxl-job-admin xxl-job-admin-1.0.tgz -n dev

说明：  
1、部署xxl-job-admin到k8s到dev命名空间下

### ingress方式暴露k8s集群外部访问 ###

创建ingress 将xxl-job-admin服务暴露到集群外部  
$vi ingress.yaml

apiVersion: extensions/v1beta1
    kind: Ingress
    metadata:
      name: xxl-job-admin-ingress
      namespace: dev
      annotations:
        kubernetes.io/ingress.class: alb
        alb.ingress.kubernetes.io/scheme: internal
      labels:
        app: xxl-job-admin-ingress
    spec:
      rules:
        - http:
            paths:
              - path: /xxl-job-admin/*
                backend:
                  serviceName: xxl-job-admin
                  servicePort: 8080

$kubectl apply -f ingress.yaml -n dev

### 测试访问 ###

以上暴露集群外部的方式是ingress，比如ingress关联的是alb，地址为：http:/alb.test.cn/  
对应的测试地址为：

http:/alb.test.cn/xxl-job-admin/

默认的账号密码：admin/123456