...
The focus is on incremental improvements in the following areas, as discussed presented at the Casablanca Architecture F2F in Vancouver:
- Persistent Storage
- pluggable persistent storage technologies to expand beyond static host path configuration + NFS backend
- evolve standardized Helm Templates (introduced in Beijing) to support global configuration and sub chart overrides of Storage Classes
- provide support for GlusterFS as the first storage class provisioner
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1228
- Resource Limits
- apply CPU and Memory limits to Helm Charts in order to improve Pod placement based on resources available in a Kubernetes Cluster
- OOM working with teams to gather accurate values per project
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1145
- Common "shared" Helm Charts
- project teams benefit from "sharing" common Helm Charts that reference common images and tested functionality
- mariadb-galera cluster
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1176 - mariadb (standalone)
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1164 - postgres cluster
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1178 - cassandra
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1177 - redis
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1179
- mariadb-galera cluster
- project teams benefit from "sharing" common Helm Charts that reference common images and tested functionality
- Platform Resiliency
- Backup and Restore Restore tools and procedures
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1232 - Node Selectors Selectors for Pod placement
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-1229
- Backup and Restore Restore tools and procedures
...