The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Severity and priority can be challenging for a company to nail. When an incident is declared, it's essential to have a system to define the impact and how urgently it should be handled. Incident severity and priority are the two knobs teams can leverage to define scope and urgency, and eventually, the appropriate process to take action. But how should we define them, and what are the differences?
Getting your pricing right is critical to the success of any SaaS company, but finding a model that works can be tough. Price too high, you won’t close enough deals - your business will fail. Price too low, your business model will be unsustainable - your business will fail. To add to the complication, when you’re a new startup your goals are evolving.
Change is critical to growth. Especially if you’re running a business in today’s volatile market. The silver lining is that we are at the peak of innovation, moving forward from a decade filled with disruptions, catalysing transformations. Over the years, enterprise IT has evolved to play a more significant role in business. Innovation, macro-economic factors, unexpected disruptions, and other internal and external factors have caused the change.
Picture yourself trying to resolve a code error when you notice an additional issue outside your realm of expertise that's making matters worse. Your instinct is to get in touch with the right contact as quickly as possible to resolve the issue so that there's no further impact on the system's uptime. But what if you can't get in touch with them immediately, or don't know who to contact? Instead of trying to solve the problem without support, a DevOps toolchain could have mitigated this chain reaction from the start.
Take a hands-on look at Tidal's brand new cloud cost optimization platform at https://saveonclouds.com.
Today we are going to explore getting started using Argo CD. This post is going to assume you know a bit about containers, and that you already have an empty cluster in place (or know how to create one). If any of this is unfamiliar, head over to Understanding the Basics to get a bit of practice. Before we get started, let’s talk about GitOps.