Financial-grade release policies
Kubernetes (K8s) deployments are stable. However, many complex, enterprise-level deployment models still rely on advanced scripts and Operations and Maintenance (O&M) tools. Rolling upgrades also fail to meet the O&M requirements of financial scenarios. SOFAStack builds on our experience with financial-grade Platform as a Service (PaaS) platforms and extends the Kubernetes deployment model with Custom Resource Definitions (CRDs). The product interface is customized for financial-grade releases, bringing the best practices for financial-grade deployment to container application services.
Application services
You can deploy application services using release orders, which provide a rich set of release policies and a one-stop deployment model. This model covers pod and container definitions, storage, networking, release policies, and Log Monitoring. It also supports version snapshots for tracing and rollbacks, allowing you to configure application services through a visual and tightly controlled interface.
Release orders
You can manage the release status and policies for one or more applications and review release changes. Any configuration change to an application service generates a version snapshot. During release preparation, you can configure application dependencies to automatically implement serial and parallel release policies. During the release, all pre-release, release, and post-release task events are recorded, which makes it easy to track the release history.
Core deployment object: CafeDeployment
CafeDeployment extends the native release capabilities of Kubernetes as a CRD. It provides cloud-native management for applications, which lets you handle complex deployments with a standard command, such as kubectl apply -f xxx.yaml.
Unitization: Application instances are deployed to separate nodes.
Fine-grained release management: Provides features such as beta releases, group-based releases, release pauses, and release cancellations during pod configuration updates.
Versioning: Automatically saves a version after each pod configuration update to simplify rollbacks.
In-place upgrades: You can change pod configurations while keeping the pod IP address unchanged.
One-stop cloud-native implementation
The container application service has passed the Cloud Native Computing Foundation (CNCF) conformance test. It provides a visual user interface (UI) for standard native Kubernetes workloads and resources, which ensures consistent Kubernetes capabilities and meets the de facto standard for container platform O&M.
The service provides end-to-end platform capabilities and supports an open ecosystem. This allows developers and O&M teams to interact with the platform using their preferred methods. The service enables seamless integration with CI/CD, code management tools, and monitoring systems. You can also experience the benefits of ServiceMesh on the container application service.
Cluster management
You can build a cluster from scratch with a single click, scale the cluster out or in at any time as needed, and use namespace management to logically isolate your services.
Metadata management
The service is compatible with native Kubernetes models such as Service, pod, and ReplicaSet. It combines these models with its own application service concept to provide richer metadata and resource management.
Network traffic
You can integrate with Server Load Balancer to forward internal traffic from load-balancing services and external traffic from Ingress to your application service pods.
Image Center
The Image Center provides image building and version management capabilities that are linked to your GitLab repository. This enables one-click builds from code to image. Integration with Identity and Access Management (IAM) ensures security.
Release and deployment
The service supports both in-place upgrades and native releases to suit different deployment scenarios.
App Store
You can use the Helm Chart App Store to orchestrate complex containerized applications with a single click.