Deploying your first app on the Kubernetes based Knative platform

With everything going on in DevOps, I think we can safely say that building pipelines is the way to deploy your applications to production. But knowing what you deploy to production and whether it is actually okay needs more data, like security checks, performance checks, and budget checks. We’ve come up with a process for that, which we call Continuous Verification “A process of querying external systems and using information from the response to make decisions to improve the development and deployment process.” In this session, we’ll look at extending an existing CI/CD pipeline with checks for security, performance, and cost to make a decision on whether we want to deploy our app or not.

In a nutshell, Continuous Verification is about putting as many automated checks as possible into your CI/CD pipelines. These checks call out to external systems to validate performance, security, and cost — without asking your engineers to do that manually. The same systems that decide whether a deployment goes to production can also help engineers understand where the bottlenecks are. More checks in the pipeline means fewer manual tasks, less overhead, and better decisions about what actually ships. And yeah, maybe a bit more time at the beach.

At VMware we define Continuous Verification as: “A process of querying external systems and using information from the response to make decisions to improve the development and deployment process.” At #OSSDay, I got a chance to not only talk about what that means for serverless apps and how you can build it into your existing pipelines using tools like GitLab, CloudHealth, Wavefront and Gotling.