Devtron Inc | Home

Devtron Escalation Matrix

Level 1: Submit a ticket through the Support Portal (Tickets are automatically escalated according to the defined SLAs for severe Devtron platform issues)

Level 2: If further escalation is needed, email cx-escalation-csm@devtron.ai to engage the Customer Success Manager.

Level 3: For critical issues that still remain unresolved, contact the CX Leadership team at cx-escalation-leadership@devtron.ai

    Priority Index


    LevelPriority Description
    P3Low Priority: General inquiries about Kubernetes or Devtron functionalities. Low-impacting and very specific use cases or feature requests. Help for third-party integrations (best effort basis).
    P2Medium Priority: Self non-production system impaired or Devtron non-critical functionalities not working. Non-critical feature requests that will enhance the Devtron system.
    P1High Priority: Self production system impaired or Devtron critical components down impacting non-production environments. Feature requests that are blocking or limiting customers' critical capabilities.
    P0Critical Incident: Self business critical production system down or Devtron critical components down impacting production.

      • Popular Articles

      • [Resolved] Workaround for resolving npm warn tar TAR_BAD_ARCHIVE: Unrecognized archive format

        Overview Recently, users have encountered issues in their Node.js builds, reporting errors such as: npm WARN tar TAR_BAD_ARCHIVE: Unrecognized archive format Request failed "304 Not Modified" (if using Yarn as the package manager). This issue has ...

      • Resolving DNS resolution issues with Coredns

        Problem statement Increase in timeouts while DNS resolution in a Kubernetes Cluster (EKS on AWS). Suspected Problem Coredns getting overwhelmed with DNS resolution requests and resolution takes multiple hops and searches thus decreasing Coredns ...

      • Git-sensor PVC- disk full

        Need to increase the PVC size if you are getting following error: Need to check the Storageclass by which PVC was provisioned. Run the following command: kubectl get storageclass Check for the field allowVolumeExpansion, if it is set to true, run the ...

      • Not able to see commits, throwing exit status 128

        1. Save the Git Repository Again Wait for few minutes and check the build pipeline if commits are visible or not 2. Check git sensor pod logs kubectl logs -n devtroncd -l app=git-sensor If you still get the same issue, try to bounce the pod and save ...

      • Refreshing ArgoCD Certificates When Expired

        1. Edit ArgoCD Secret Use kubectl edit to edit the ArgoCD secret in the appropriate namespace (devtroncd in this case). Find the data section and delete the lines for tls.crt and tls.key: kubectl edit secret argocd-secret -n devtroncd 2. Delete Lines ...