website·Indexed 34 days ago
https://openkruise.io/An extended component suite for Kubernetes focused on automating application management. It includes OpenKruiseGame (OKG) for cloud-native game server management on Kubernetes, Kruise Rollouts for progressive delivery (canary, blue-green, and A/B testing), and specialized controllers like CloneSet, AdvancedStatefulSet, and GameServerSet.
On-demand volume mounting allows developers to declare one or more existing Persistent Volumes (PVs) to be mounted into a sandbox at the time of claiming. This is an alternative to provisioning a new PVC per sandbox via volumeClaimTemplates.
Key characteristics:
agent-runtime and CSI sidecars injected into the sandbox Pod.NodeSelector. This ensures pods are scheduled to the target domain. Currently, it supports StatefulSet, Advanced StatefulSet, CloneSet, and Deployment as workload types.apiVersion: apps.kruise.io/v1alpha1
kind: UnitedDeployment
metadata:
name: sample-ud
spec:
replicas: 6
selector:
matchLabels:
app: sample
template:
statefulSetTemplate:
metadata:
labels:
app: sample
spec:
selector:
matchLabels:
app: sample
template:
metadata:
labels:
app: sample
spec:
containers:
- image: nginx:alpine
name: nginx
topology:
subsets:
- name: subset-a
nodeSelectorTerm:
matchExpressions:
- key: node
operator: In
values:
- zone-a
replicas: 1
- name: subset-b
nodeSelectorTerm:
matchExpressions:
- key: node
operator: In
values:
- zone-b
replicas: 50%
- name: subset-c
nodeSelectorTerm:
matchExpressions:
- key: node
operator: In
values:
- zone-cv1beta1 and v1alpha1 versions starting from Kruise v1.9.0.apiVersion: apps.kruise.io/v1beta1
kind: AdvancedCronJob
spec:
template:
# Choose one of the following:
jobTemplate: { ... }
broadcastJobTemplate: { ... }
imageListPullJobTemplate: { ... }volumeClaimTemplates to ensure user configuration files and working data are preserved across sandbox recreations.Deployment, ReplicaSet, Job, and CloneSet. Unlike Pod Topology Spread Constraints, it supports exact customized partition numbers and proportions and maintains these distributions during scale-down events. Unlike UnitedDeployment, it is a lightweight configuration that associates with existing workloads rather than requiring a new workload type.