Create your FREE Codefresh account and start making pipelines fast. Create Account

Survey Says: COVID-19 is Threatening On-prem Environments

3 min read

COVID-19 is leading to large-scale migrations away from on-premises environments, according to Codefresh’s second annual State of DevOps survey that revealed this and other surprising insights into the continued evolution of the industry. At the same time, DevOps automation continues to expand in scope and complexity with more and more processes becoming automated, and more involved technologies like Kubernetes continuing to gain strong traction. While it has improved some year-over-year, most organizations are still struggling with implementing and maintaining automation.

Key takeaways from the survey include:

  •  COVID-19 has led many to reconsider their on-prem infrastructure strategy

Codefresh asked how COVID-19 has affected DevOps professional’s plans to reconsider their on-prem infrastructure strategy, with somewhat surprising results. 58% of respondents saying that due to the pandemic, they are planning on moving some infrastructure to the cloud with 17% of respondents planning to move their entire stack to the cloud.

In total, about 75% of respondents said that they are moving at least part of their infrastructure to the cloud as a result of the COVID-19 pandemic, representing a dramatic shift in strategy and further adoption towards the cloud.

  • DevOps budgets are going up in 2020

74% of respondents are expecting an increase and more than half are expecting their budgets to increase by 25% or more.

Organizations are continuing to invest heavily in their DevOps budgets as the effect of DevOps on developer velocity and site reliability continues to be better understood.

  • Most companies are still struggling with commit-to-production automation (although it’s getting better)

If your organization is struggling with complete commit-to-production automation, you’re not alone. Automation proves to be elusive as less than 5% of respondents claimed that all of their company’s DevOps processes are automated from Git commit to code running in production.

52% of respondents have less than 50% of their organization’s DevOps process automated from Git commit to production. This is down from last year’s survey, where 66% of respondents had less than 50% of their processes automated. This represents the continued trend away from manual processes as organizations build out their DevOps automation.

  • Kubernetes continues to build momentum, with most thinking that it will be used on more than half of new projects by the end of 2020

73% of respondents said that they believe that by the end of 2020, more than half of new projects will use Kubernetes.

In 2019’s survey, 54% of respondents said that Kubernetes would be used in more than half of all projects by the end of the year. Clearly, Kubernetes adoption is continuing to accelerate.

75% of respondents said that they have either already adopted Kubernetes or are planning to adopt Kubernetes soon.

  • 67% of DevOps engineers spend over a quarter of their time just fixing bugs in their automated systems

67% of respondents said that they spend 25% or more of their time fixing bugs in their automated systems, while 35% of respondents spend 50% or more of their time fixing bugs in their automated systems.

This highlights the importance of choosing a well-architected DevOps automation stack, as the platform you use can have a massive impact on the amount of time lost to bug fixing.

Dan Garfield

Dan is the Co-Founder and Chief Open Source Officer at Codefresh. His work in open source includes being an Argo Maintainer, and co-chair of the GitOps Working Group. As a technology leader with a background in full-stack engineering, evangelism, and communications, he led Codefresh's go-to-market strategy and now leads open source strategy. You can follow him at

4 responses to “Survey Says: COVID-19 is Threatening On-prem Environments

  1. Ron Teeter says:


    The vertical axis on the “How much engineering time is spent fixing bugs?” chart doesn’t seem to cover the 25% – 50% section that I suspect would contain quite a few respondent’s data. Was it intentionally removed for clarity or a miss?

    1. Taryn Jones says:

      Hi Ron. Thank you for the comment. This was initially modified for clarity but has now been corrected.

  2. I may have missed it, but what did the surveyed demographics look like? How many, what actual roles, and how large the organization?. Thanks

    1. Dan Garfield says:

      As I recall it was a pretty good mix of mid to larger size companies but we’re working on a new survey so it might be best to wait for that one.

Leave a Reply

* All fields are required. Your email address will not be published.