Blogs

For the last couple of years, we’ve been working to implement Kanban philosophies of work for our teams at Kerkhoff Technologies Inc.

In the rush to create web applications and sites that look snazzy and are functional, something that often gets overlooked is basic user experience in regards to performance.

“After 10 years in our previous office, we moved into our new office this past August. We had the opportunity to make it our own.

Richard will be giving a 30-minute presentation on combining DevOps and ChatOps at Chilliwack.tech‘s /Next event on coming Saturday, November 17th.

So you know all about Kubernetes and how it manages your containers, hosts your ingresses, mounts your volumes, schedules your jobs, feeds your dog and makes your coffee.

What should you do when you’ve developed and installed a cron job for your Kubernetes application, and you need to test it?

At Crafty Penguins, we work with software development teams to automate their processes and infrastructure, so that they can deploy software updates at least daily instead of monthly or yearly, all the while maintaining a high level of up-time and security.

In our client’s DevOps journey, we are shooting for an efficient, stable, and reactive development-to-production workflow in your infrastructure. Let’s talk about the Continuous Improvement/Continuous Development (CI/CD) phase along the journey!

We’ve talked already about two parts of the journey: “Works for me” and Continuous Improvement / Continuous Development (CI/CD). This time, we’ll talk about the importance of an effective staging environment in which to test a bunch of stuff before going into production.

We’ve talked about why stuff breaks in the production environment when it didn’t in development (see “Works for me”), how Continuous Improvement / Continuous Deployment helps in failure detection, and how we can set up a “like-production” staging environment in which to test your features.

We have talked about specific types of pain: things breaking in the production environment that didn’t in the development environment, which we called “Works for me;” taking too long to get features out the door, which we solve with continuous improvement / continuous development; and the pain of not having a staging environment in which to properly test features before rolling to production.

This is the last post in the 6-post series on the Crafty Penguins DevOps Journey we take our clients on.