Prepare production grade deployments of 3rd-party applications without forking.
It’s never been easier to configure and deploy 3rd-party k8s applications.
Pull in the chart you want
Begin by pulling in the chart from the upstream maintainer which will include the default
Add your custom values to the
values.yaml that make it possible for your application to run.
These values will override the defaults in the upstream chart and your base directory is created.
Write your patch file
Patches give you the flexibility to overrite any values from the upstream chart. Say good bye to templating.
Let Ship do the hard work
Replicated Ship + Kustomize does the heavy lifting to merge your patch, and generate your Kubernetes YAML.
Replicated Ship is good for any workflow thanks to three powerful commands.
Initialize an application by pulling in the chart and set up the base directory (generally run on a workstation).
Observes an upstream repo or application for updates (best run as a CRD or in a cron type process).
Pull the latest from the upstream repo, consumes state.json to generate the deployable assets.
Replicated ship was built with first-class support for Helm charts designed to automate the “last-mile” of custom configuration via Kustomize. In addition you can now do things like support GitOps in your cluster, provide messaging in your lifecycle and so much more.