Value Statement
By specifying storage limits for containers, we prevent storage resource contention, ensure fair resource distribution, and avoid potential outages due to runaway storage consumption.
Targeted Files (TBD):
- [ ]
Definition of Done for Engineering Story Owner (Checklist)
- [ ] Storage limits are defined for containers in Kubernetes configuration files.
- [ ] Storage allocation aligns with application requirements and storage class configurations.
- [ ] Pods are successfully deployed and tested with storage limits enforced.
Noncompliant code example
apiVersion: v1
kind: Pod
metadata:
name: example
spec:
containers:
- name: web # Noncompliant
image: nginx
volumeMounts:
- name: ephemeral
mountPath: "/tmp"
Compliant solution
apiVersion: v1 kind: Pod metadata: name: example spec: containers: - name: web image: nginx resources: limits: ephemeral-storage: "2Gi" volumeMounts: - name: ephemeral mountPath: "/tmp"
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- clones
-
ACM-9999 MCH: Specify storage limits for containers in YAML configuration files to prevent runaway storage usage and ensure fair resource distribution
- Closed