You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often when deploying applications to production environments, DevOps teams need to assess how resilient a workload is for a production environment. This can include things such as its availability, resilience, disaster response, etc. Devtron is looking to implement a mechanism to generate a scorecard that gives a number from 0-100 to denote how ready a workload is for production environments. This scorecard can help a user understand what are the best practices being followed, and what further steps can be taken to improve the production readiness for the workload. Some examples of the criteria include:
Pod - Topology Spread to ensure spread across multiple AZs
Description
Often when deploying applications to production environments, DevOps teams need to assess how resilient a workload is for a production environment. This can include things such as its availability, resilience, disaster response, etc. Devtron is looking to implement a mechanism to generate a scorecard that gives a number from 0-100 to denote how ready a workload is for production environments. This scorecard can help a user understand what are the best practices being followed, and what further steps can be taken to improve the production readiness for the workload. Some examples of the criteria include:
Deliverable
Analyse a list of set criteria that will analyze the application and generate a scorecard to determine the production readiness for a deployment.
In the scope
Implement a basic scoring mechanism that assesses readiness based on simple criteria such as
Future Scope
In the future, we would like to add additional criteria for creating the score card such as
Key Competencies
Recommended Skills to have:
Mentors
Skill Level: Easy, Medium
Time: ~175 hrs
The text was updated successfully, but these errors were encountered: