Operations | Monitoring | ITSM | DevOps | Cloud

The Rancher Academy launched on May 15, 2020. Here we are, 94 days later, and we’ve issued our 1,000th certificate to a graduate of the Certified Rancher Operator: Level 1 course. Rancher is open source software, so anyone can download it and use it. With that freedom, though, comes a cost: we all learn how to use it according to how we need to use it. Through this lens, the actual potential of Rancher becomes distorted, and the experience of each individual varies widely.

We’ve all been on two types of projects: ones that ran smoothly, and ones that crumbled to pieces. While there are lots of contributing factors in each case, I’ll go out on a limb and say that project ownership (or lack thereof) is what makes the biggest difference.

Growth is generally considered to be a healthy characteristic of a business. But, if the firm cannot establish systems that can take care of that growth, it might end up digging a hole for its operations.

Kubernetes as a project is maturing, support has been increased from nine to 12 months, and there’s a new protocol in place to ensure a steady progress on feature development. Also, many of its new features are meant to improve the quality of life of its users, like Generic ephemeral inline volumes, or the structured logging.

Developers understand the importance of keeping their team up to date on work and use many of the integrations between Bitbucket Cloud and Jira like smart commits and automation triggers to do so automatically. However there may be times where there are nuances or uncommon situations when merging a pull request that aren't covered by existing automation rules – sometimes there are multiple pull requests, or sometimes merging means you're now in 'Done' and other times you're in 'Releasing'.