This article outlines the steps teams will need to execute in order to begin a supported trial.
Supported trials include a consultation with a Solutions Engineer, customized test cases and working collaboratively to create an ROI analysis and Business value assessment.
If you are interested in getting support for your evaluation, setup a demo and ask to talk to an SE.
1) Identification of evaluation clusters
Select 2-4 high-activity clusters that are used by the target audiences for the evaluation
| If your Use Case is | And your Target Audience is | We Recommended | Why This Matters |
| Reducing MTTR | SREs, Platform Engineers, DevOps | Production | Production issues directly impact reliability KPIs and customer satisfaction. |
| Shift Left / Dev Exp. | Developers, Application Teams, Product Teams | Dev / Test / Staging (Primary)Production (Optional) | Highlights real developer workflow challenges; shows value in faster iteration cycles. |
| Optimizing Costs | Engineering, FinOps, SREs |
Staging/Dev (Primary) Production (to be discussed) |
You need optimization across your fleet and you want to do it in a safe and reliable way. You also have different requirements to optimize production vs staging/dev. Staging/dev tends to be overlooked and have the highest propensity for cost impact. |
| The use cases are additive (you may have all 3!) Choose clusters where the target audience operates day-to-day and ensure the environment reflects their real-world challenges. Select clusters that are representative of the challenges your want to solve for (MTTR reduction, cost optimization, shifting devs to the right, etc) | |||
2) Creating your Komodor account & initial admin user
-
Select a person who you want to be a Komodor admin for your account
- Other users can also be granted admin permissions when invited
- Have that person go to https://app.komodor.com/
-
Select ‘Sign up’ and then 'Create Account'
- The initial signup here creates both the organizational Komodor account, as well as the user’s personal account.
- After account creation, notify your Komodor SE so they can adjust required settings (i.e. uptier, extended expiration)
3) Komodor Agent installation in evaluation clusters
Komodor agents are deployed as a daemonset of each of the clusters you want to monitor and troubleshoot, and easily deployed with a helm chart.
- Complete the instructions in How To: Connecting a Komodor Agent to a Cluster
4) Inviting additional users to your Komodor account
Once you have setup your account in Step #2, that user can then invite other users into the account
-
Complete the instructions in How To: Invite/Add A New User
Comments
0 comments
Article is closed for comments.