ShuttleOps, a provider of a namesake no-code continuous integration/continuous delivery (CI/CD) platform, announced today it has made that platform available on Kubernetes.
Company CEO David Found says organizations want to accelerate the rate at which they can develop applications without having to employ an IT operations team just to install and manage the CI/CD platform on which those applications are constructed and deployed.
A no-code solution based on a series of wizards eliminates the need to master tasks such as how to employ YAML files to deploy software on a Kubernetes cluster, he notes. ShuttleOps also provides support for global management of environment variables and container arguments.
The CI/CD platform also secures application secrets and configures cloud firewalls, eliminating the need for out-of-band processes. There’s also support for Chef Habitat to package non-containerized applications when necessary, Found says.
Finally, ShuttleOps also provides support for ConfigMaps, Secrets and Ingress Controllers, as well as provisioning of Kubernetes namespaces and rolling deployments.
ShuttleOps can be deployed either in a self-managed Kubernetes environment or on a managed Kubernetes service provided by Amazon Web Services (AWS), Microsoft or Google. The goal is to make it easier for any organization to become “a software company” by eliminating all the overhead associated with deploying a CI/CD platform, he says. Given the complexity of earlier CI/CD platforms, Found notes many organizations now have entire IT teams dedicated to managing their DevOps platforms. A no-code alternative dramatically reduces the total cost of DevOps by eliminating the need for those teams, he says.
The CI/CD platform from ShuttleOps is available in a free community edition for up to five users along with a professional edition priced at $250 per 10 app components/containers per month and a professional edition priced at $2,500 annually per 10 app components/containers.
Once the overhead associated with deploying a DevOps platform is eliminated, he says, developers can deploy and manage their own CI/CD environments, which in turn accelerates the rate at which applications can be built and deployed. It’s effectively a way to bring best DevOps practices to all developers rather than a select few, he adds.
It’s unclear how many IT organizations that have already standardized on a CI/CD platform would be willing to switch that one out for an easier-to-manage alternative. Many organizations are already employing existing CI/CD platforms running on legacy platforms to build both monolithic and microservices-based applications. The one thing that is certain is there are plenty of greenfield deployments of Kubernetes clusters where no CI/CD platform yet exists. As the pressure to build and update microservices faster intensifies, the number of teams that might opt to deploy a CI/CD platform that runs natively on Kubernetes could substantially increase.
Regardless of the path chosen, there’s no doubt the rise of microservices will drive more organizations to embrace best DevOps practices. The challenge now is determining what CI/CD platform best enables them to achieve that goal.