Operations | Monitoring | ITSM | DevOps | Cloud

July 2022

Qovery x Spayr - Managing Multiple Environments Running on Kubernetes Clusters

Qovery makes it easy to deploy on-demand environments on AWS. More than 20,000 DevOps and developers use Qovery to deploy their production, staging, and development environments on AWS in a few seconds. Join Albane (Product Marketing at Qovery) and Pierre (CTO and Co-founder at Spayr) to talk about how Spayr is managing multiple environments running on Kubernetes clusters on Qovery, and is empowering his team, from junior to senior developers, to create a new environment and test new ideas independently.

Spayr Manages Multiple Environments On Kubernetes With Qovery

Albane here, Product Marketing Manager at Qovery 👋 Yesterday we joined forced Pierre Olive (CTO and co-founder of Spayr) to talk about how they manage multiple environments on Kubernetes with Qovery and much more; if you missed it or would just rather read than listen, here is the recap.

Why Preview Environments Are The New Thing in DevOps

Consider the scenario where a complex product is being developed by dozens of engineers working on different features of a product. Not only the development environment is the same, but the staging environment is also shared. As different features are merged into the shared environment, they break the code. So QA has to wait until this is fixed. A feature or bug fix may be working perfectly on the developer’s own machine, but there is no way for the QA team to test that one feature in isolation.

Everything You Need to Know About Deployment Environments

It's common practice that development environments for the same product are kept the same (or at least compatible) for smooth software development life cycle (SDLC) workflow. That brings the question, why do we need more than one environment for the same product. In today’s modern software development, it is crucial for product development teams to maintain an effective and rapid workflow if they want to gain a competitive edge in the product market.

Why DevOps Engineers Love and Recommend Qovery

My team and I built Qovery to empower DevOps engineers and Developers to better work together - without compromises. In 2022, DevOps engineers need to build reliable infrastructure on top of the best cloud service providers (e.g. AWS, Azure, GCP), dealing with security concerns, productivity, reliability, and many services. DevOps engineers are responsible for a lot of things in an organization. From CI/CD, to the run of the apps in production and the backup of databases.

3 Pro Tips To Get The Most Out Of Qovery - Part 1

Some people spend hours on a spreadsheet and call themselves “Excell Ninja” here at Qovery; we spend hours on our console because, in case you don’t know yet, we test and deploy using Qovery for Qovery. After a year of using our console almost every day, I started to make a list of all the small tips and tricks that I was able to gather, and because sharing is caring, here are my top three tips to use on Qovery.

Kubernetes Cluster Autoscaler vs Karpenter

One of the most exciting things when using Kubernetes is the ability to scale up and down the number of nodes based on application consumption. So you don’t have to manually add and remove nodes on demand and let it go on usage. Obviously what you want is to keep control on the minimum and the maximum number of nodes to avoid an unexpected bill.

Q2 2022 product retrospective - Last quarter's top features

The second quarter is now over and after the start of our V3 at the beginning of this quarter we are super happy to announce that it’s now out in Alpha but there is so much more to speak about so without further due, let me show you all the great things we achieve during the past quarter 🚀