Operations | Monitoring | ITSM | DevOps | Cloud

We get it, installing Artifactory and the JFrog DevOps Platform on Kubernetes can be daunting. As easy as we’ve sought to make it with our official JFrog installation Helm charts, there are a lot of decisions to be made. That’s meant to give you the widest possible choice for how to best fit your JFrog installation to your infrastructure. But choice can be overwhelming, too.

Continuous Deployment (CD) requires setting up your infrastructure and automation to update your solution with the latest code change from the main branch. That’s what we call “Liquid Software”. Full automation makes your deployment seamless, less error prone, faster and it makes the feedback loop shorter because you can now deploy after each change. Achieving continuous deployment requires the following elements.

Ownership isn’t for everyone — building and maintaining an abode is a lot of trouble when all you need is a place to hang your hat. That can also be true when you’re a creator of Helm charts. You’ll certainly want the benefits of a Helm chart repository to store, version, and share your charts for deploying applications to Kubernetes.

Research firm IDC has recently published an infographic (check it out below!) outlining the new requirements for modern software distribution and key guidance for organizations to meet future needs and overcome the bottlenecks in the next era of large-scale application delivery. With the advent of DevOps and modern delivery practices, organizations are becoming better at rapidly developing and deploying new applications to better serve their customers and stay competitive in today’s digital age.

If you’re using the JFrog DevOps Platform to manage your software artifacts, then there’s a good chance that one of the clients you’re already using is JFrog CLI. JFrog CLI is a robust tool, which enhances and extends the capabilities of the JFrog Platform, by connecting it to your build and automation agents.