The latest News and Information on DevOps, CI/CD, Automation and related technologies.
The modernization of infrastructure and applications is driving the rapid growth of containers, and as companies scale the adoption of Kubernetes, it’s critical to incorporate security and compliance. The challenge? Compliance and security is a journey, not a state in time, and application security in Kubernetes has a large surface area. This challenge increases exponentially as you run more applications, onboard more developers, add more environments, add new pipelines, and more.
Government agencies are facing a rising need for changes to their IT infrastructure. This need is becoming even more urgent as they continue to migrate operations to the cloud. Leveraging modern cloud applications and resources within an existing legacy agency environment requires IT agility to maintain the balance of security while keeping pace with an agency’s mission.
There are a number of lessons I learned guiding weeks-long backcountry leadership courses for teens that I carried with me into my roles in incident management. In this blog post, I’ll share three that stand out.
As we continue to build our vision around Shipa Insights, we are pleased to announce that we are now including engineering efficiency statistics along with the policy and security violations from our initial release. Getting started with Shipa Insights is very easy, Shipa Insights is there for you automatically. Navigate to the Insights Module and take a look at what Shipa has been keeping track of / discovering on your behalf.
Kubernetes shouldn’t be reserved for production. Using local Kubernetes in development means you can build and test your service using the same technologies as your live deployments. Some organizations provide a shared Kubernetes cluster for development activities. Others offer on-demand virtual clusters that serve staging environments for significant changes.
The software industry is moving toward teams that own the services they build. This concept encloses principles and possibilities from movements toward microservices, DevOps, Agile, and Project to Product. In these paradigms, a team of people delivers software that provides valued capabilities. These capabilities help customers get their work done, support business operations, or enable other software to do these.