What’s New in SREWorks v1.1? Streamlined Deployment, Plug‑in Storage, and Low‑Code Templates

Since the open‑source release of SREWorks v1.0 in March, the team collected feedback via DingTalk, WeChat, and GitHub, and prioritized the top three issues for v1.1: storage plug‑in, minimal‑resource deployment, and storage class usage, while also addressing minor bugs.

Future releases will continue a rapid cadence to quickly resolve user pain points and help build intelligent operations platforms on cloud‑native infrastructure.

1. Base Edition / Intelligent Edition

Because Kubernetes clusters can be resource‑intensive, v1.1 separates the base and intelligent applications, allowing users to experience only the SREWorks platform without the heavier intelligent modules.

The base edition runs on a single 4‑core, 16 GB machine.

Base edition includes eight applications:

Operations Middleware

Application Management

Team Management

Cluster Management

Template Center

Help Center

File Management

System Settings

Intelligent edition adds seven applications:

Data Operations Platform

Intelligent Operations Platform

Self‑Healing

Health Management

Operations Center

Job Scheduling Platform

Operations Search

Deploy the base edition with Helm by adding the following parameter (the intelligent edition is the default):

--set saas.onlyBase=true

2. Component Plug‑in: ElasticSearch / MySQL / MinIO

Many production environments already have reliable storage modules such as ES, MySQL, or MinIO, and users may prefer to inject their own endpoints instead of using the built‑in storage of SREWorks v1.0. The team extracted these storage modules into configurable variables.

Use the following Helm parameters to replace storage components as needed:

# Replace the primary MySQL for base applications
--set appmanager.server.database.host="*.mysql.rds.aliyuncs.com" 
--set appmanager.server.database.password="****" 
--set appmanager.server.database.user="root" 
--set appmanager.server.database.port=3306 
--set appmanagerbase.mysql.enabled=false

# Replace the MySQL for intelligent applications
--set saas.dataops.dbHost="*.mysql.rds.aliyuncs.com" 
--set saas.dataops.dbUser=root 
--set saas.dataops.dbPassword="*****" 
--set saas.dataops.dbPort=3306

# Replace the ElasticSearch for intelligent applications
--set saas.dataops.esHost="*.public.elasticsearch.aliyuncs.com" 
--set saas.dataops.esPort="9200" 
--set saas.dataops.esUser="elastic" 
--set saas.dataops.esPassword="*******"

# Replace MinIO for base applications
--set global.minio.accessKey="*******" 
--set global.minio.secretKey="*******" 
--set appmanager.server.package.endpoint="minio.*.com:9000" 
--set appmanagerbase.minio.enabled=false

3. Page Template Center

The low‑code front‑end development model can be a barrier for users unfamiliar with the platform. To lower this barrier, the team organized front‑end components into reusable templates based on common scenarios, allowing users to import a ready‑made page and continue development on top of it. Users can also save their own pages as templates to improve daily development efficiency.

4. Default StorageClass Support

Many Kubernetes users are unclear about StorageClass logic, leading to time‑consuming troubleshooting. After evaluating community storage solutions, v1.1 adopts an OpenEBS‑based LocalPV as the default, reducing usage cost.

Important: If you already have a custom storage class or a storage pool in your cluster, disable the default OpenEBS storage class to avoid directory contention.

Disable the default StorageClass with the following Helm parameters (example uses the Alibaba Cloud ACK storage class alicloud-disk-available):

--set appmanagerbase.openebs.enabled=false
--set global.storageClass="alicloud-disk-available"

5. Other Optimizations

Fixed backend microservice edit page errors

Added default authentication toggle for backend microservices

Resolved deletion errors in operations applications

Fixed idempotent exception on repeated appmanager initialization

Addressed import errors in productopsv2 under slow NFS databases

Changed data source password fields to password input type

6. How to Upgrade to v1.1

Upgrade includes the platform base; expect 5‑10 minutes of page unavailability.

User‑developed cloud‑native applications remain unaffected (no restart), but traffic through the SREWorks gateway may be interrupted.

git clone http://github.com/alibaba/sreworks.git -b v1.1 sreworks
cd sreworks
./sbin/upgrade-cluster.sh --kubeconfig="****"