Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-366

Containers must crash properly when a failure occurs

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: High High
    • Guilin Release
    • None
    • None
    • Containers must crash properly when a failure occurs
    • Non-Functional Requirement (DEPRECATED)
    • 1
    • Not yet performed
    • Original Scope
    • M
    • GO
    • Yellow
    • GO
    • Green
    • GO
    • Yellow
    • GO

       Description of Use Case / Requirement:

       Kubernetes best practice mandates that when an issue occurs (no access to Database, REST mandatory call fails, bug in code, ...), the container must crash with exit code different than 0

       

      Owners (one of these should be the Assignee - use @ notation): kopasiak sdesbure

       

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

       

      Project Impact (Test Only (TO), Code (C)):

       

      Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

      Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

       

      Integration Leads (use @ notation): 

       

      Company Engagement: Samsung, Orange

       

        1. image-2020-07-30-16-01-06-149.png
          image-2020-07-30-16-01-06-149.png
          18 kB

            sdesbure sdesbure
            sdesbure sdesbure
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: