SchedulerX:Deploy SchedulerX in a Kubernetes cluster

Step 1: Configure RBAC

SchedulerX Kubernetes tasks authenticate through a ServiceAccount. Apply the following RBAC configuration once per cluster and namespace.

Single-namespace scheduling: Use a Role and RoleBinding to restrict SchedulerX to one namespace.

apiVersion: v1
kind: ServiceAccount
metadata:
  name: schedulerx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: schedulerx-role
rules:
  - apiGroups: [""]
    resources: ["pods"]
    verbs: ["create","delete","get","list","patch","update","watch"]
  - apiGroups: [""]
    resources: ["pods/log"]
    verbs: ["get","list","watch"]
  - apiGroups: [""]
    resources: ["configmaps"]
    verbs: ["create","delete","get","list","patch","update"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["watch"]
  - apiGroups: ["batch"]
    resources: ["jobs","cronjobs"]
    verbs: ["create","delete","get","list","patch","update","watch"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: schedulerx-binding
subjects:
  - kind: ServiceAccount
    name: schedulerx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: schedulerx-role

Cross-namespace scheduling: Use a ClusterRole and ClusterRoleBinding to schedule Pods and Jobs across multiple namespaces.

apiVersion: v1
kind: ServiceAccount
metadata:
  name: schedulerx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: schedulerx-cluster-role
rules:
  - apiGroups: [""]
    resources: ["pods"]
    verbs: ["create","delete","get","list","patch","update","watch"]
  - apiGroups: [""]
    resources: ["pods/log"]
    verbs: ["get","list","watch"]
  - apiGroups: [""]
    resources: ["configmaps"]
    verbs: ["create","delete","get","list","patch","update"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["watch"]
  - apiGroups: ["batch"]
    resources: ["jobs","cronjobs"]
    verbs: ["create","delete","get","list","patch","update","watch"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: schedulerx-cluster-binding
subjects:
  - kind: ServiceAccount
    name: schedulerx
    namespace: <NAMESPACE1>
  - kind: ServiceAccount
    name: schedulerx
    namespace: <NAMESPACE2>
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: schedulerx-cluster-role

Step 2: Deploy the SchedulerX agent

Save the following YAML as schedulerx-agent.yaml, replace the environment variable placeholders, and apply it with kubectl apply -f schedulerx-agent.yaml.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: schedulerx-agent
  labels:
    app: schedulerx-agent
spec:
  replicas: 1
  selector:
    matchLabels:
      app: schedulerx-agent
  template:
    metadata:
      labels:
        app: schedulerx-agent
    spec:
      serviceAccountName: schedulerx
      containers:
      - name: schedulerx-agent
        image: schedulerx-registry.cn-hangzhou.cr.aliyuncs.com/schedulerx2/agent:latest-amd64
        imagePullPolicy: Always
        resources:
          requests:
            cpu: 500m
        env:
          - name: "SCHEDULERX_ENDPOINT"
            value: "<your-endpoint>"
          - name: "SCHEDULERX_NAMESPACE"
            value: "<your-namespace-id>"
          - name: "SCHEDULERX_GROUPID"
            value: "<your-application-id>"
          - name: "SCHEDULERX_APPKEY"
            value: "<your-application-key>"
          - name: "SCHEDULERX_STARTER_MODE"
            value: "pod"
        livenessProbe:
          exec:
            command: ["/bin/bash","/root/health.sh"]
          timeoutSeconds: 30
          initialDelaySeconds: 30

Replace the following placeholders with your actual values:

Step 3: Verify the deployment

1. Check that the agent Pod is running:

   kubectl get pods -l app=schedulerx-agent

   Expected output:

   NAME                               READY   STATUS    RESTARTS   AGE
   schedulerx-agent-xxxxxxxxx-xxxxx   1/1     Running   0          30s

2. Confirm the connection in the SchedulerX console: go to the Application Management page and verify that the instance appears as connected.

Step 1: Download the Helm chart

wget https://schedulerx2.oss-cn-hangzhou.aliyuncs.com/helm/schedulerxchart-2.0.0.tgz

Step 2: Get connection parameters

1. Log on to the Distributed Task Scheduling Platform console.

2. In the top navigation bar, select a region.

3. In the left navigation pane, click Application Management.

4. Find your application and click Connection Settings in the Actions column. In the upper-left corner of the Connection Settings page, select Kubernetes.

Step 3: Install the chart

Run the following command with your connection parameters from the previous step.

helm install schedulerxchart schedulerxchart-2.0.0.tgz \
  --set SCHEDULERX_ENDPOINT=acm.aliyun.com\
  ,SCHEDULERX_NAMESPACE=f856c3f8-a15c-4a7e-9b4e-f812a9f8****\
  ,SCHEDULERX_GROUPID=k8s-test3\
  ,SCHEDULERX_APPKEY=****\
  ,SCHEDULERX_AGENT_IMAGE=schedulerx-registry.cn-hangzhou.cr.aliyuncs.com/schedulerx2/agent:latest-amd64

Step 4: Verify the deployment

After installation completes, confirm the agent Pod is running:

kubectl get pods -l app=schedulerx-agent

Then check the Application Management page in the SchedulerX console to verify the instance is connected.

Step 1: Add Maven dependencies

Add the Spring Boot starter and the Kubernetes plugin to your pom.xml. For the latest version number, see Release notes.

<dependency>
  <groupId>com.aliyun.schedulerx</groupId>
  <artifactId>schedulerx2-spring-boot-starter</artifactId>
  <version>${schedulerx2.version}</version>
</dependency>
<dependency>
  <groupId>com.aliyun.schedulerx</groupId>
  <artifactId>schedulerx2-plugin-kubernetes</artifactId>
  <version>${schedulerx2-plugin-kubernetes.version}</version>
</dependency>

Step 2: Connect to SchedulerX

Follow the instructions in Connect a Spring Boot application to SchedulerX.