** Work in Progress**
Architecture Changes since Beijing
There are no significant architecture changes for OOM in the Casablanca release.
The focus for this release is in the following areas:
- Persistent Storage
- pluggable persistent storage technologies
- standardized Helm Templates (introduced in Beijing) evolved slightly to support global configuration and sub chart overrides of Storage Classes
- delivering support for GlusterFS
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1228
- Resource Limits
- CPU and Memory limits per Helm Chart
- Improves Pod placement based on resources available to a Kubernetes Cluster
- OOM working with project teams for accurate values
- Common "shared" Helm Charts
- mariadb-galera cluster
- postgres
- cassandra
- ELK
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1101
- Platform Resiliency
- Backup and Restore
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1232 - Node Selectors
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1229 - Enable (Anti)Affinity Rules
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1231
- Backup and Restore
Software Changes since Beijing
Upgrading from Helm 2.8.2 to 2.9.1.
Upgrading from Kubernetes 1.8.10 to ???
Docker 17.03.x to ???API Updates
OOM does not provide any external APIs.
S3P Updates
Information/Data Model Alignment
No impact on OOM.